summaryrefslogtreecommitdiffstats
path: root/drivers/bluetooth
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2014-07-04 16:54:38 +0200
committerJohan Hedberg <johan.hedberg@intel.com>2014-07-04 18:09:34 +0300
commit4739b5b185aad15b5c52c39e789ff582ec20796b (patch)
tree919bc2701e2e1916f3553dbd73c312764bb7ea0a /drivers/bluetooth
parent89bc22d23f63c2d437f677d7eae0fa922bedcdcb (diff)
downloadop-kernel-dev-4739b5b185aad15b5c52c39e789ff582ec20796b.zip
op-kernel-dev-4739b5b185aad15b5c52c39e789ff582ec20796b.tar.gz
Bluetooth: Set HCI_QUIRK_INVALID_BADDR for Intel USB default address
When the Intel USB controller has a default address, then set the quirk so the Bluetooth core knows that controller configuration is required. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Diffstat (limited to 'drivers/bluetooth')
-rw-r--r--drivers/bluetooth/btusb.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 3244e31..825f3e1 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -1216,9 +1216,11 @@ static int btusb_check_bdaddr_intel(struct hci_dev *hdev)
* fully operational, but have the danger of duplicate addresses
* and that in turn can cause problems with Bluetooth operation.
*/
- if (!bacmp(&rp->bdaddr, BDADDR_INTEL))
+ if (!bacmp(&rp->bdaddr, BDADDR_INTEL)) {
BT_ERR("%s found Intel default device address (%pMR)",
hdev->name, &rp->bdaddr);
+ set_bit(HCI_QUIRK_INVALID_BDADDR, &hdev->quirks);
+ }
kfree_skb(skb);
OpenPOWER on IntegriCloud