Bluetooth: controller: Initialize PDUs in set #0 on reset
Set #0 is used for legacy advertising when legacy HCI commands are used and in such case it's possible to enable advertising without any prior configuration. This means we should better always have PDUs in set #0 initialized with default empty data. Signed-off-by: Andrzej Kaczmarek <andrzej.kaczmarek@codecoup.pl>
This commit is contained in:
parent
55698d26b6
commit
9d8503c3b1
2 changed files with 43 additions and 0 deletions
|
@ -810,6 +810,15 @@ struct bt_hci_cp_le_set_random_address {
|
|||
#define BT_HCI_ADV_DIRECT_IND_LOW_DUTY 0x04
|
||||
#define BT_HCI_ADV_SCAN_RSP 0x04
|
||||
|
||||
#define BT_LE_ADV_INTERVAL_MIN 0x0020
|
||||
#define BT_LE_ADV_INTERVAL_MAX 0x4000
|
||||
#define BT_LE_ADV_INTERVAL_DEFAULT 0x0800
|
||||
|
||||
#define BT_LE_ADV_CHAN_MAP_CHAN_37 0x01
|
||||
#define BT_LE_ADV_CHAN_MAP_CHAN_38 0x02
|
||||
#define BT_LE_ADV_CHAN_MAP_CHAN_39 0x04
|
||||
#define BT_LE_ADV_CHAN_MAP_ALL 0x07
|
||||
|
||||
#define BT_LE_ADV_FP_NO_WHITELIST 0x00
|
||||
#define BT_LE_ADV_FP_WHITELIST_SCAN_REQ 0x01
|
||||
#define BT_LE_ADV_FP_WHITELIST_CONN_IND 0x02
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue