Bluetooth: Adding driver and quirk defs for multi-role LE
This change adds the relevant driver and quirk to allow drivers to report the le_states as being trustworthy. This has historically been disabled as controllers did not reliably support this. In particular, this will be used to relax this condition for controllers that have been well tested and reliable. /* Most controller will fail if we try to create new connections * while we have an existing one in slave role. */ if (hdev->conn_hash.le_num_slave > 0) return NULL; Signed-off-by: Alain Michaud <alainm@chromium.org> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:
parent
c03ee9af4e
commit
220915857e
|
@ -58,6 +58,7 @@ static struct usb_driver btusb_driver;
|
|||
#define BTUSB_CW6622 0x100000
|
||||
#define BTUSB_MEDIATEK 0x200000
|
||||
#define BTUSB_WIDEBAND_SPEECH 0x400000
|
||||
#define BTUSB_VALID_LE_STATES 0x800000
|
||||
|
||||
static const struct usb_device_id btusb_table[] = {
|
||||
/* Generic Bluetooth USB device */
|
||||
|
|
|
@ -218,6 +218,15 @@ enum {
|
|||
* This quirk must be set before hci_register_dev is called.
|
||||
*/
|
||||
HCI_QUIRK_WIDEBAND_SPEECH_SUPPORTED,
|
||||
|
||||
/* When this quirk is set, the controller has validated that
|
||||
* LE states reported through the HCI_LE_READ_SUPPORTED_STATES are
|
||||
* valid. This mechanism is necessary as many controllers have
|
||||
* been seen has having trouble initiating a connectable
|
||||
* advertisement despite the state combination being reported as
|
||||
* supported.
|
||||
*/
|
||||
HCI_QUIRK_VALID_LE_STATES,
|
||||
};
|
||||
|
||||
/* HCI device flags */
|
||||
|
|
Loading…
Reference in New Issue