diff options
author | Marcel Holtmann <marcel@holtmann.org> | 2014-07-04 16:54:38 +0200 |
---|---|---|
committer | Johan Hedberg <johan.hedberg@intel.com> | 2014-07-04 18:09:34 +0300 |
commit | 4739b5b185aad15b5c52c39e789ff582ec20796b (patch) | |
tree | 919bc2701e2e1916f3553dbd73c312764bb7ea0a /drivers/bluetooth/btusb.c | |
parent | 89bc22d23f63c2d437f677d7eae0fa922bedcdcb (diff) | |
download | linux-4739b5b185aad15b5c52c39e789ff582ec20796b.tar.bz2 |
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/btusb.c')
-rw-r--r-- | drivers/bluetooth/btusb.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c index 3244e311ca29..825f3e16651f 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); |