Bluetooth: Introduce HCI_QUIRK_STRICT_DUPLICATE_FILTER
Some vendors decide to use a strict duplicate filter policy that only filters on Bluetooth device addresses. This means that when the RSSI changes, these devices are not reported again. During discovery it is useful to actually get the RSSI updates. Since this is specific to each controller, add a new quirk setting that allows drivers to tell the core what kind of filtering policy the controller uses. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
868ed8e06a
commit
43d6bc46e2
|
@ -129,6 +129,15 @@ enum {
|
||||||
* during the hdev->setup vendor callback.
|
* during the hdev->setup vendor callback.
|
||||||
*/
|
*/
|
||||||
HCI_QUIRK_INVALID_BDADDR,
|
HCI_QUIRK_INVALID_BDADDR,
|
||||||
|
|
||||||
|
/* When this quirk is set, the duplicate filtering during
|
||||||
|
* scanning is based on Bluetooth devices addresses. To allow
|
||||||
|
* RSSI based updates, restart scanning if needed.
|
||||||
|
*
|
||||||
|
* This quirk can be set before hci_register_dev is called or
|
||||||
|
* during the hdev->setup vendor callback.
|
||||||
|
*/
|
||||||
|
HCI_QUIRK_STRICT_DUPLICATE_FILTER,
|
||||||
};
|
};
|
||||||
|
|
||||||
/* HCI device flags */
|
/* HCI device flags */
|
||||||
|
|
Loading…
Reference in New Issue