Bug#674565: Bluetooth activation failed (btusb module)

2012-05-29 Thread Arief M Utama 
On Tue, May 29, 2012 at 2:07 AM, Jonathan Nieder jrnie...@gmail.com wrote:

 Arief M Utama wrote:
  On Sun, May 27, 2012 at 1:35 AM, Jonathan Nieder jrnie...@gmail.com
 wrote:

   Will look around and then submit these
  for inclusion in 3.2.y from kernel.org if they seem to be well tested.
 
  I can test the other patches if needed, just to make sure about it :-)

 Yeah, no need.

 For the future: it now occurs to me that you might have been applying
 the patches with the test-patches script one at a time, which would
 explain why some of them didn't apply.  The command takes a list of
 patches as arguments to apply in order.  But it's not important: I was
 asking to test them together just as a while at it extra in the same
 boot.  I don't think it's worth the time to compile and boot yet
 again. :)


Noted :-)





 I need to finish gathering a list of people who tested the driver
 using hardware with the other USB ids and then I'll send the patches
 as a batch to stable@.  Thanks for your help and sorry to be so slow
 at this.


You're very helpful and prompt already, I'm being a bit slow here.



 Sincerely,
 Jonathan



All the best.
-arief

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-29 Thread Arief M Utama 
On Tue, May 29, 2012 at 3:57 AM, Jonathan Nieder jrnie...@gmail.com wrote:

 Arief M Utama wrote:

  Hit enter too quick, forgot about the dmesg attachment. Here it is.

 Wonderful, thanks.  Just for fun, let's parse some unrelated messages.

  [0.00] DMI: Hewlett-Packard HP ENVY 15 NOTEBOOK PC/1688, BIOS
 F.04 11/12/2011
 [...]
  [2.529762] \_SB_.PCI0:_OSC invalid UUID
  [2.529763] _OSC request data:1 8 1f
 [...]
  [2.573816] \_SB_.PCI0:_OSC invalid UUID
  [2.573817] _OSC request data:1 1f 1f
  [2.573820]  pci:00: Requesting ACPI _OSC control (0x1d)
  [2.573865] \_SB_.PCI0:_OSC invalid UUID
  [2.573866] _OSC request data:1 0 1d
  [2.573869]  pci:00: ACPI _OSC request failed (AE_ERROR),
 returned control mask: 0x1d
  [2.573871] ACPI _OSC control for PCIe not granted, disabling ASPM

 That's https://bugzilla.kernel.org/show_bug.cgi?id=36932, perhaps.
 Could be a bug in the BIOS or an ACPI bug in the kernel, or a
 misleading message.


How can I help with this one? Not very familiar with kernel debugging.



 [...]
  [   10.250808] rts_pstor: module is from the staging directory, the
 quality is unknown, you have been warned.
  [   10.251583] Initializing Realtek PCIE storage driver...
 [...]
  [   11.452078] rts_pstor: device scan complete
  [   11.452316] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S.
 1.00 PQ: 0 ANSI: 0 CCS
  [   11.452417] Bad LUN (0:1)
  [   11.452607] Bad target number (1:0)
  [   11.452746] Bad target number (2:0)
  [   11.452878] Bad target number (3:0)
  [   11.452998] Bad target number (4:0)
  [   11.453141] Bad target number (5:0)
  [   11.453257] Bad target number (6:0)
  [   11.453353] Bad target number (7:0)
  [   11.453724] sd 6:0:0:0: [sdb] Attached SCSI removable disk

 http://bugs.debian.org/637813.  I get the impression that Realtek
 has abandoned this driver and is working on a new version (not
 published yet) that follows a different approach.


And how about this one? Do you happen to know where I can check the new
drivers? I tried to read the bug comments, but I got lost in the woods
there.



 [...]
  [   77.448484] atkbd serio0: Unknown key pressed (translated set 2, code
 0xab on isa0060/serio0).
  [   77.448494] atkbd serio0: Use 'setkeycodes e02b keycode' to make it
 known.

 If this is the brightness key, sounds like
 https://bugzilla.redhat.com/804285.  There is a related upstream
 report at https://bugzilla.kernel.org/show_bug.cgi?id=43280.



Yep it's brightness key, used setkeycodes to ignore it. What is the
debian-way to put in some customs boot-time scripts?

All that is not working in this laptop now are HP's Wireless Audio usb
device (snd-usb-audio module?) I had to blacklist it, since it keep sending
messages to the console and prevent pulseaudio from running which in turn
prevent gnome-shell to run, and the other one is the presence-censor that
activates keyboard light whenever it detect objects in-front of the screen,
but since I can pressed function key to activate the keyboard light this is
not much of a hassle.



 Thanks,
 Jonathan


All the best.
-arief

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-29 Thread Jonathan Nieder 
Arief M Utama wrote:
 On Tue, May 29, 2012 at 3:57 AM, Jonathan Nieder jrnie...@gmail.com wrote:
 Arief M Utama wrote:

 [0.00] DMI: Hewlett-Packard HP ENVY 15 NOTEBOOK PC/1688, BIOS F.04 
 11/12/2011
 [...]
 [2.529762] \_SB_.PCI0:_OSC invalid UUID
[...]
 [2.573869]  pci:00: ACPI _OSC request failed (AE_ERROR), returned 
 control mask: 0x1d
 [2.573871] ACPI _OSC control for PCIe not granted, disabling ASPM

 That's https://bugzilla.kernel.org/show_bug.cgi?id=36932, perhaps.
 Could be a bug in the BIOS or an ACPI bug in the kernel, or a
 misleading message.

 How can I help with this one? Not very familiar with kernel debugging.

Best way is to contact the linux-acpi list (linux-a...@vger.kernel.org)
and ask for advice.

Second-best is to attach your logs and add yourself to the cc list for
https://bugzilla.kernel.org/show_bug.cgi?id=36932 so you'd be informed
if someone asks people to test patches.

[...]
 http://bugs.debian.org/637813.  I get the impression that Realtek
 has abandoned this driver and is working on a new version (not
 published yet) that follows a different approach.

 And how about this one? Do you happen to know where I can check the new
 drivers? I tried to read the bug comments, but I got lost in the woods
 there.

I don't think they're public yet.
http://thread.gmane.org/gmane.linux.drivers.driver-project.devel/26300/focus=1298462

[...]
 If this is the brightness key, sounds like
 https://bugzilla.redhat.com/804285.  There is a related upstream
 report at https://bugzilla.kernel.org/show_bug.cgi?id=43280.

 Yep it's brightness key, used setkeycodes to ignore it. What is the
 debian-way to put in some customs boot-time scripts?

I dunno. :)  /etc/rc.local, maybe?

 All that is not working in this laptop now are HP's Wireless Audio usb
 device (snd-usb-audio module?) I had to blacklist it, since it keep sending
 messages to the console and prevent pulseaudio from running which in turn
 prevent gnome-shell to run,

Is this a regression (i.e., did it ever work)?  Please do file a report
when convenient.

Ciao,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-28 Thread Arief M Utama 
On Sun, May 27, 2012 at 1:35 AM, Jonathan Nieder jrnie...@gmail.com wrote:

 Arief M Utama wrote:

  This is the output from lsusb:
 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp.
  Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp.
  Bus 004 Device 004: ID 064e:e258 Suyin Corp.
 
  More details from lsusb output on the bluetooth device attached.

 Thanks.

  I can confirm that patch number 4
  [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working
 on
  my laptop. Haven't tested other patches, although I can report that only
  patches 1, 4, 6 and 8 that applied successfully.

 Ok.  What kernel are you applying these to?  Could you attach dmesg
 output from the patched kernel?


The source package was called this:  linux-2.6-3.2.18, the image is this:
linux-image-3.2.0-2-amd64.

dmesg output attached here.

I was hoping to get a quick sanity check that the other patches at
 least didn't cause the kernel to explode :), but answers to more
 important questions about them would indeed require info from people
 with the matching hardware.  Will look around and then submit these
 for inclusion in 3.2.y from kernel.org if they seem to be well tested.


I can test the other patches if needed, just to make sure about it :-)



 Hope that helps,
 Jonathan



All the best.
-arief

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-28 Thread Jonathan Nieder 
Arief M Utama wrote:
 On Sun, May 27, 2012 at 1:35 AM, Jonathan Nieder jrnie...@gmail.com wrote:

  Will look around and then submit these
 for inclusion in 3.2.y from kernel.org if they seem to be well tested.

 I can test the other patches if needed, just to make sure about it :-)

Yeah, no need.

For the future: it now occurs to me that you might have been applying
the patches with the test-patches script one at a time, which would
explain why some of them didn't apply.  The command takes a list of
patches as arguments to apply in order.  But it's not important: I was
asking to test them together just as a while at it extra in the same
boot.  I don't think it's worth the time to compile and boot yet
again. :)

I need to finish gathering a list of people who tested the driver
using hardware with the other USB ids and then I'll send the patches
as a batch to stable@.  Thanks for your help and sorry to be so slow
at this.

Sincerely,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-28 Thread Jonathan Nieder 
Arief M Utama wrote:

 Hit enter too quick, forgot about the dmesg attachment. Here it is.

Wonderful, thanks.  Just for fun, let's parse some unrelated messages.

 [0.00] DMI: Hewlett-Packard HP ENVY 15 NOTEBOOK PC/1688, BIOS F.04 
 11/12/2011
[...]
 [2.529762] \_SB_.PCI0:_OSC invalid UUID
 [2.529763] _OSC request data:1 8 1f 
[...]
 [2.573816] \_SB_.PCI0:_OSC invalid UUID
 [2.573817] _OSC request data:1 1f 1f 
 [2.573820]  pci:00: Requesting ACPI _OSC control (0x1d)
 [2.573865] \_SB_.PCI0:_OSC invalid UUID
 [2.573866] _OSC request data:1 0 1d 
 [2.573869]  pci:00: ACPI _OSC request failed (AE_ERROR), returned 
 control mask: 0x1d
 [2.573871] ACPI _OSC control for PCIe not granted, disabling ASPM

That's https://bugzilla.kernel.org/show_bug.cgi?id=36932, perhaps.
Could be a bug in the BIOS or an ACPI bug in the kernel, or a
misleading message.

[...]
 [   10.250808] rts_pstor: module is from the staging directory, the quality 
 is unknown, you have been warned.
 [   10.251583] Initializing Realtek PCIE storage driver...
[...]
 [   11.452078] rts_pstor: device scan complete
 [   11.452316] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S.   1.00 
 PQ: 0 ANSI: 0 CCS
 [   11.452417] Bad LUN (0:1)
 [   11.452607] Bad target number (1:0)
 [   11.452746] Bad target number (2:0)
 [   11.452878] Bad target number (3:0)
 [   11.452998] Bad target number (4:0)
 [   11.453141] Bad target number (5:0)
 [   11.453257] Bad target number (6:0)
 [   11.453353] Bad target number (7:0)
 [   11.453724] sd 6:0:0:0: [sdb] Attached SCSI removable disk

http://bugs.debian.org/637813.  I get the impression that Realtek
has abandoned this driver and is working on a new version (not
published yet) that follows a different approach.

[...]
 [   77.448484] atkbd serio0: Unknown key pressed (translated set 2, code 0xab 
 on isa0060/serio0).
 [   77.448494] atkbd serio0: Use 'setkeycodes e02b keycode' to make it 
 known.

If this is the brightness key, sounds like
https://bugzilla.redhat.com/804285.  There is a related upstream
report at https://bugzilla.kernel.org/show_bug.cgi?id=43280.

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-26 Thread Arief M Utama 
Hi Jonathan,

First, thanks for the reply.

On Fri, May 25, 2012 at 11:20 PM, Jonathan Nieder jrnie...@gmail.comwrote:

 # hardware support
 severity 674565 important
 tags 674565 + upstream patch moreinfo
 quit

 Hi Arief,

 Arief M Utama wrote:

  This is a minor but annoying bug,
  btusb on my HP Envy 15 laptop failed to activate bluetooth,
  since it lacks the appropriate usb_device_id entry.
 
  I would propose adding the entry for more convinience and usability.
  Currently I have to use some commands to activate the bluetooth module
  by adding the ID entry on related sysfs file.
 
  Err, upon examining the code I found that the entry already existed in
  current 3.2 kernel source file (drivers/bluetooth/btusb.c) but looks
  like it is a typo error.

 Thanks.  Please attach lsusb output.

 If you have time to test the attached patch series following
 instructions from [1], that would also be very useful.



This is the output from lsusb:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp.
Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp.
Bus 004 Device 004: ID 064e:e258 Suyin Corp.

More details from lsusb output on the bluetooth device attached.

I can confirm that patch number 4
[0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working on
my laptop. Haven't tested other patches, although I can report that only
patches 1, 4, 6 and 8 that applied successfully.


All the best.
-arief
Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp. 
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  255 Vendor Specific Class
  bDeviceSubClass 1 
  bDeviceProtocol 1 
  bMaxPacketSize064
  idVendor   0x0a5c Broadcom Corp.
  idProduct  0x21e1 
  bcdDevice1.12
  iManufacturer   1 
  iProduct2 
  iSerial 3 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  218
bNumInterfaces  4
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  1 
  bInterfaceProtocol  1 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  1 
  bInterfaceProtocol  1 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x  1x 0 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-26 Thread Jonathan Nieder 
Arief M Utama wrote:

 This is the output from lsusb:

 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp.
 Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp.
 Bus 004 Device 004: ID 064e:e258 Suyin Corp.

 More details from lsusb output on the bluetooth device attached.

Thanks.

 I can confirm that patch number 4
 [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working on
 my laptop. Haven't tested other patches, although I can report that only
 patches 1, 4, 6 and 8 that applied successfully.

Ok.  What kernel are you applying these to?  Could you attach dmesg
output from the patched kernel?

I was hoping to get a quick sanity check that the other patches at
least didn't cause the kernel to explode :), but answers to more
important questions about them would indeed require info from people
with the matching hardware.  Will look around and then submit these
for inclusion in 3.2.y from kernel.org if they seem to be well tested.

Hope that helps,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-25 Thread Jonathan Nieder 
# hardware support
severity 674565 important
tags 674565 + upstream patch moreinfo
quit

Hi Arief,

Arief M Utama wrote:

 This is a minor but annoying bug,
 btusb on my HP Envy 15 laptop failed to activate bluetooth,
 since it lacks the appropriate usb_device_id entry.

 I would propose adding the entry for more convinience and usability.
 Currently I have to use some commands to activate the bluetooth module
 by adding the ID entry on related sysfs file.

 Err, upon examining the code I found that the entry already existed in
 current 3.2 kernel source file (drivers/bluetooth/btusb.c) but looks
 like it is a typo error.

Thanks.  Please attach lsusb output.

If you have time to test the attached patch series following
instructions from [1], that would also be very useful.

Hope that helps,
Jonathan

[1] 
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
or the corresponding page in the debian-kernel-handbook package
From: Manoj Iyer manoj.i...@canonical.com
Date: Thu, 2 Feb 2012 09:32:36 -0600
Subject: Bluetooth: btusb: Add vendor specific ID (0a5c 21f3) for BCM20702A0

commit 37305cf649689a4d2341dd6fd89b091c6007f9ba upstream.

T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=03 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a5c ProdID=21f3 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=74DE2B344A7B
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

Signed-off-by: Manoj Iyer manoj.i...@canonical.com
Tested-by: Dennis Chua dennis.c...@canonical.com
Acked-by: Marcel Holtmann mar...@holtmann.org
Signed-off-by: Johan Hedberg johan.hedb...@intel.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
 drivers/bluetooth/btusb.c |1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index e56da6a34700..1f8c8ca9e87e 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -102,6 +102,7 @@ static struct usb_device_id btusb_table[] = {
 
/* Broadcom BCM20702A0 */
{ USB_DEVICE(0x0a5c, 0x21e3) },
+   { USB_DEVICE(0x0a5c, 0x21f3) },
{ USB_DEVICE(0x413c, 0x8197) },
 
{ } /* Terminating entry */
-- 
1.7.10

From: James M. Leddy james.le...@canonical.com
Date: Tue, 6 Mar 2012 02:41:33 +0200
Subject: Bluetooth: btusb: add support for BCM20702A0 [0a5c:21e6]

commit 0a4eaeeb993658a4d6cff054a863241f32d3d2fb upstream.

Add another vendor specific ID for BCM20702A0.  This has been tested and
works on hardware with this device.

output of usb-devices:
T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=04 Dev#= 6 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a5c ProdID=21e6 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=D0DF9AFB227B
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

Signed-off-by: James M. Leddy james.le...@canonical.com
Acked-by: Marcel Holtmann mar...@holtmann.org
Signed-off-by: Andrew Morton a...@linux-foundation.org
Signed-off-by: Johan Hedberg johan.hedb...@intel.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
 drivers/bluetooth/btusb.c |1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 1f8c8ca9e87e..fde7512da775 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -102,6 +102,7 @@ static struct usb_device_id btusb_table[] = {
 
/* Broadcom BCM20702A0 */
{ USB_DEVICE(0x0a5c, 0x21e3) },
+   { USB_DEVICE(0x0a5c, 0x21e6) },
{ USB_DEVICE(0x0a5c, 0x21f3) },
{ USB_DEVICE(0x413c, 0x8197) },
 
-- 
1.7.10

From: João Paulo Rechi Vita jprv...@openbossa.org
Date: Wed, 14 Mar 2012 21:45:16 +0200
Subject: Bluetooth: btusb: Add USB device ID 0a5c 21e8

commit 6dfc326f0605fd87e4c10ccde10de0ce4280d72d upstream.

One more vendor-specific ID for BCM20702A0.

T:  Bus=01 Lev=03 Prnt=05 Port=02 Cnt=01 Dev#=  9 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0a5c ProdID=21e8 Rev=01.12
S:  Manufacturer=Broadcom Corp
S:  Product=BCM20702A0
S:  SerialNumber=00027221F4E2
C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

Signed-off-by: João