summaryrefslogtreecommitdiffstats
path: root/drivers/bluetooth/hci_ath.c
diff options
context:
space:
mode:
authorAdam Lee <adam.lee@canonical.com>2015-01-28 15:30:27 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-03-06 14:52:44 -0800
commita73e33ea08a2f684d1e7d2bf8db98acadac72116 (patch)
tree32ad2adbc40fddb5ed6ba0239d6568a7d85f1a5f /drivers/bluetooth/hci_ath.c
parente5c9f0bba1c8efb828fbc895f9ff436bcd7cac61 (diff)
downloadlinux-stable-a73e33ea08a2f684d1e7d2bf8db98acadac72116.tar.gz
linux-stable-a73e33ea08a2f684d1e7d2bf8db98acadac72116.tar.bz2
linux-stable-a73e33ea08a2f684d1e7d2bf8db98acadac72116.zip
Bluetooth: ath3k: workaround the compatibility issue with xHCI controller
commit c561a5753dd631920c4459a067d22679b3d110d6 upstream. BugLink: https://bugs.launchpad.net/bugs/1400215 ath3k devices fail to load firmwares on xHCI buses, but work well on EHCI, this might be a compatibility issue between xHCI and ath3k chips. As my testing result, those chips will work on xHCI buses again with this patch. This workaround is from Qualcomm, they also did some workarounds in Windows driver. Signed-off-by: Adam Lee <adam.lee@canonical.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/bluetooth/hci_ath.c')
0 files changed, 0 insertions, 0 deletions