Bluetooth: Use USB_VENDOR_AND_INTERFACE() for Broadcom devices
authorGustavo Padovan <gustavo.padovan@collabora.co.uk>
Mon, 6 Aug 2012 18:36:49 +0000 (15:36 -0300)
committerGustavo Padovan <gustavo.padovan@collabora.co.uk>
Tue, 21 Aug 2012 17:46:44 +0000 (14:46 -0300)
Many Broadcom devices has a vendor specific devices class, with this rule
we match all existent and future controllers with this behavior.

We also remove old rules to that matches product id for Broadcom devices.

Tested-by: John Hommel <john.hommel@hp.com>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
drivers/bluetooth/btusb.c

index 2fe7776dc49cb88aba9c69c06715b3f3c0aa5622..e791b20beaf5b90cc3ad8f63ef94f6dd29325e5a 100644 (file)
@@ -94,16 +94,14 @@ static struct usb_device_id btusb_table[] = {
 
        /* Broadcom BCM20702A0 */
        { USB_DEVICE(0x0489, 0xe042) },
-       { USB_DEVICE(0x0a5c, 0x21e3) },
-       { USB_DEVICE(0x0a5c, 0x21e6) },
-       { USB_DEVICE(0x0a5c, 0x21e8) },
-       { USB_DEVICE(0x0a5c, 0x21f3) },
-       { USB_DEVICE(0x0a5c, 0x21f4) },
        { USB_DEVICE(0x413c, 0x8197) },
 
        /* Foxconn - Hon Hai */
        { USB_DEVICE(0x0489, 0xe033) },
 
+       /*Broadcom devices with vendor specific id */
+       { USB_VENDOR_AND_INTERFACE_INFO(0x0a5c, 0xff, 0x01, 0x01) },
+
        { }     /* Terminating entry */
 };