Skip to content

Commit 2d13e34

Browse files
jwrdegoedeholtmann
authored andcommitted
Revert "Bluetooth: btusb: Add workaround for Broadcom devices without product id"
Commit 9834e58 ("Bluetooth: btusb: Add workaround for Broadcom devices without product id") was added to deal with the BT part of the BCM4356A2 on GPD pocket laptops having an usb vid:pid of 0000:0000. After another commit to add support for the BCM UART connected BT ACPI-id BCM2E7E used on the GPD win, it turns out that the BT on the GPD pocket is connected via both USB and UART. Adding support for the BCM2E7E ACPI-id causes it to switch to UART mode. The Windows shipped with the device is using it in UART mode and the presence of the BCM2E7E ACPI-id combined with the all 0 USB vid:pid indicates that the BT part was never meant to be used in USB mode. With the recent patches to use serdev device enumeration / instantiation for UART attached ACPI enumerated BT devices, everything work OOTB in UART mode and the workaround for the all 0 USB vid:pid is no longer needed. This reverts commit 9834e58 ("Bluetooth: btusb: Add workaround for Broadcom devices without product id"). Signed-off-by: Hans de Goede <[email protected]> Signed-off-by: Marcel Holtmann <[email protected]>
1 parent 61d220a commit 2d13e34

File tree

1 file changed

+0
-18
lines changed

1 file changed

+0
-18
lines changed

drivers/bluetooth/btusb.c

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,6 @@ static struct usb_driver btusb_driver;
6666
#define BTUSB_BCM2045 0x40000
6767
#define BTUSB_IFNUM_2 0x80000
6868
#define BTUSB_CW6622 0x100000
69-
#define BTUSB_BCM_NO_PRODID 0x200000
7069

7170
static const struct usb_device_id btusb_table[] = {
7271
/* Generic Bluetooth USB device */
@@ -171,10 +170,6 @@ static const struct usb_device_id btusb_table[] = {
171170
{ USB_VENDOR_AND_INTERFACE_INFO(0x0930, 0xff, 0x01, 0x01),
172171
.driver_info = BTUSB_BCM_PATCHRAM },
173172

174-
/* Broadcom devices with missing product id */
175-
{ USB_DEVICE_AND_INTERFACE_INFO(0x0000, 0x0000, 0xff, 0x01, 0x01),
176-
.driver_info = BTUSB_BCM_PATCHRAM | BTUSB_BCM_NO_PRODID },
177-
178173
/* Intel Bluetooth USB Bootloader (RAM module) */
179174
{ USB_DEVICE(0x8087, 0x0a5a),
180175
.driver_info = BTUSB_INTEL_BOOT | BTUSB_BROKEN_ISOC },
@@ -2909,19 +2904,6 @@ static int btusb_probe(struct usb_interface *intf,
29092904
if (id->driver_info == BTUSB_IGNORE)
29102905
return -ENODEV;
29112906

2912-
if (id->driver_info & BTUSB_BCM_NO_PRODID) {
2913-
struct usb_device *udev = interface_to_usbdev(intf);
2914-
2915-
/* For the broken Broadcom devices that show 0000:0000
2916-
* as USB vendor and product information, check that the
2917-
* manufacturer string identifies them as Broadcom based
2918-
* devices.
2919-
*/
2920-
if (!udev->manufacturer ||
2921-
strcmp(udev->manufacturer, "Broadcom Corp"))
2922-
return -ENODEV;
2923-
}
2924-
29252907
if (id->driver_info & BTUSB_ATH3012) {
29262908
struct usb_device *udev = interface_to_usbdev(intf);
29272909

0 commit comments

Comments
 (0)