LL Privacy support
Subsystems (2)
v3 cover LL Privacy support
v3: rebased the patches
Add support to enable LL privacy using mgmt with existing set_privacy command
Marcel Holtmann (3):
Bluetooth: Translate additional address type correctly
Bluetooth: Configure controller address resolution if available
Bluetooth: Update resolving list when updating whitelist
Sathish Narasimman (5):
Bluetooth: Translate additional address type during le_conn
Bluetooth: Let controller creates RPA during le create conn
Bluetooth: Enable/Disable address resolution during le create conn
Bluetooth: Enable RPA Timeout
Bluetooth: Add support to enable LL PRIVACY using set_privacy
include/net/bluetooth/hci.h | 9 ++- include/net/bluetooth/hci_core.h | 3 + net/bluetooth/hci_conn.c | 7 +- net/bluetooth/hci_core.c | 17 +++++ net/bluetooth/hci_event.c | 22 ++++++ net/bluetooth/hci_request.c | 123 +++++++++++++++++++++++++++---- net/bluetooth/hci_request.h | 3 +- net/bluetooth/mgmt.c | 8 +- 8 files changed, 170 insertions(+), 22 deletions(-)
Signature · 1 line
2.17.1
PATCH v3 1/8 Bluetooth: Translate additional address type correctly
From: Marcel Holtmann <[email protected]>
When using controller based address resolution, then the new address types 0x02 and 0x03 are used. These types need to be converted back into either public address or random address types.
--- include/net/bluetooth/hci.h | 6 ++++-- net/bluetooth/hci_core.c | 9 +++++++++ 2 files changed, 13 insertions(+), 2 deletions(-)
include/net/bluetooth/hci.h +4 -2
@@ -2268,8 +2268,10 @@ struct hci_ev_le_conn_complete {#define LE_EXT_ADV_SCAN_RSP 0x0008#define LE_EXT_ADV_LEGACY_PDU 0x0010 -#define ADDR_LE_DEV_PUBLIC 0x00 -#define ADDR_LE_DEV_RANDOM 0x01 +#define ADDR_LE_DEV_PUBLIC 0x00 +#define ADDR_LE_DEV_RANDOM 0x01 +#define ADDR_LE_DEV_PUBLIC_RESOLVED 0x02 +#define ADDR_LE_DEV_RANDOM_RESOLVED 0x03#define HCI_EV_LE_ADVERTISING_REPORT 0x02struct hci_ev_le_advertising_info {
net/bluetooth/hci_core.c +9 -0
@@ -3292,6 +3292,15 @@ struct hci_conn_params *hci_pend_le_action_lookup(struct list_head *list, {struct hci_conn_params *param; +switch (addr_type) { +case ADDR_LE_DEV_PUBLIC_RESOLVED : + addr_type =ADDR_LE_DEV_PUBLIC ; +break ; +case ADDR_LE_DEV_RANDOM_RESOLVED : + addr_type =ADDR_LE_DEV_RANDOM ; +break ; + } +list_for_each_entry (param, list, action) {if (bacmp (¶m->addr, addr) ==0 && param->addr_type == addr_type)
Signature · 1 line
2.17.1
PATCH v2 2/8 Bluetooth: Configure controller address resolution if available
In reply to Sathish NarasimmanFrom: Marcel Holtmann <[email protected]>
When the LL Privacy support is available, then as part of enabling or disabling passive background scanning, it is required to set up the controller based address resolution as well.
Since only passive background scanning is utilizing the whitelist, the address resolution is now bound to the whitelist and passive background scanning. All other resolution can be easily done by the host stack.
--- include/net/bluetooth/hci_core.h | 3 +++ net/bluetooth/hci_request.c | 26 +++++++++++++++++++++++--- 2 files changed, 26 insertions(+), 3 deletions(-)
include/net/bluetooth/hci_core.h +3 -0
@@ -1358,6 +1358,9 @@ void hci_conn_del_sysfs(struct hci_conn *conn);#define scan_coded (dev) (((dev)->le_tx_def_phys & HCI_LE_SET_PHY_CODED) || \ ((dev)->le_rx_def_phys & HCI_LE_SET_PHY_CODED)) +/* Use LL Privacy based address resolution if supported */ +#define use_ll_privacy (dev) ((dev)->le_features[0] & HCI_LE_LL_PRIVACY) +/* Use ext scanning if set ext scan param and ext scan enable is supported */ #define use_ext_scan (dev) (((dev)->commands[37] & 0x20) && \ ((dev)->commands[37] & 0x40))
net/bluetooth/hci_request.c +23 -3
@@ -675,6 +675,12 @@ void hci_req_add_le_scan_disable(struct hci_request *req) cp.enable =LE_SCAN_DISABLE ;hci_req_add (req,HCI_OP_LE_SET_SCAN_ENABLE ,sizeof (cp), &cp); } + +if (use_ll_privacy (hdev) && +hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION )) { +__u8 enable =0x00 ; +hci_req_add (req,HCI_OP_LE_SET_ADDR_RESOLV_ENABLE ,1 , &enable); + } } static void del_from_white_list(struct hci_request *req, bdaddr_t *bdaddr,
@@ -815,7 +821,8 @@ static bool scan_use_rpa(struct hci_dev *hdev) }static void hci_req_start_scan (struct hci_request *req,u8 type,u16 interval, -u16 window,u8 own_addr_type,u8 filter_policy) +u16 window,u8 own_addr_type,u8 filter_policy, +bool addr_resolv) {struct hci_dev *hdev = req->hdev;
@@ -824,6 +831,11 @@ static void hci_req_start_scan(struct hci_request *req, u8 type, u16 interval,return ; } +if (use_ll_privacy (hdev) && addr_resolv) { +u8 enable =0x01 ; +hci_req_add (req,HCI_OP_LE_SET_ADDR_RESOLV_ENABLE ,1 , &enable); + } +/* Use ext scanning if set ext scan param and ext scan enable is * supported */
@@ -897,12 +909,18 @@ static void hci_req_start_scan(struct hci_request *req, u8 type, u16 interval, } } +/* Ensure to call hci_req_add_le_scan_disable() first to disable the +* controller based address resolution to be able to reconfigure +* resolving list. +*/ void hci_req_add_le_passive_scan (struct hci_request *req) {struct hci_dev *hdev = req->hdev;u8 own_addr_type;u8 filter_policy;u16 window, interval; +/* Background scanning should run with address resolution */ +bool addr_resolv = true;if (hdev->scanning_paused) {bt_dev_dbg (hdev,"Scanning is paused for suspend" );
@@ -948,7 +966,7 @@ void hci_req_add_le_passive_scan(struct hci_request *req)bt_dev_dbg (hdev,"LE passive scan with whitelist = %d" , filter_policy);hci_req_start_scan (req,LE_SCAN_PASSIVE , interval, window, - own_addr_type, filter_policy); + own_addr_type, filter_policy, addr_resolv); }static u8 get_adv_instance_scan_rsp_len (struct hci_dev *hdev,u8 instance)
@@ -2747,6 +2765,8 @@ static int active_scan(struct hci_request *req, unsigned long opt)u8 own_addr_type;/* White list is not used for discovery */ u8 filter_policy =0x00 ; +/* Discovery doesn't require controller address resolution */ +bool addr_resolv = false;int err;BT_DBG ("%s" , hdev->name);
@@ -2768,7 +2788,7 @@ static int active_scan(struct hci_request *req, unsigned long opt) own_addr_type =ADDR_LE_DEV_PUBLIC ;hci_req_start_scan (req,LE_SCAN_ACTIVE , interval,DISCOV_LE_SCAN_WIN , - own_addr_type, filter_policy); + own_addr_type, filter_policy, addr_resolv);return 0 ; }
Signature · 1 line
2.17.1
PATCH v3 3/8 Bluetooth: Update resolving list when updating whitelist
In reply to Sathish NarasimmanFrom: Marcel Holtmann <[email protected]>
When the whitelist is updated, then also update the entries of the resolving list for devices where IRKs are available.
--- net/bluetooth/hci_request.c | 41 +++++++++++++++++++++++++++++++++++-- 1 file changed, 39 insertions(+), 2 deletions(-)
net/bluetooth/hci_request.c +39 -2
@@ -694,6 +694,21 @@ static void del_from_white_list(struct hci_request *req, bdaddr_t *bdaddr,bt_dev_dbg (req->hdev,"Remove %pMR (0x%x) from whitelist" , &cp.bdaddr, cp.bdaddr_type);hci_req_add (req,HCI_OP_LE_DEL_FROM_WHITE_LIST ,sizeof (cp), &cp); + +if (use_ll_privacy (req->hdev)) { +struct smp_irk *irk; + + irk =hci_find_irk_by_addr (req->hdev, bdaddr, bdaddr_type); +if (irk) { +struct hci_cp_le_del_from_resolv_list cp; + + cp.bdaddr_type = bdaddr_type; +bacpy (&cp.bdaddr, bdaddr); + +hci_req_add (req,HCI_OP_LE_DEL_FROM_RESOLV_LIST , +sizeof (cp), &cp); + } + } }/* Adds connection to white list if needed. On error, returns -1. */
@@ -714,7 +729,7 @@ static int add_to_white_list(struct hci_request *req,return -1 ;/* White list can not be used with RPAs */ -if (!allow_rpa && +if (!allow_rpa && !use_ll_privacy (hdev) &&hci_find_irk_by_addr (hdev, ¶ms->addr, params->addr_type)) {return -1 ; }
@@ -732,6 +747,28 @@ static int add_to_white_list(struct hci_request *req, cp.bdaddr_type);hci_req_add (req,HCI_OP_LE_ADD_TO_WHITE_LIST ,sizeof (cp), &cp); +if (use_ll_privacy (hdev)) { +struct smp_irk *irk; + + irk =hci_find_irk_by_addr (hdev, ¶ms->addr, + params->addr_type); +if (irk) { +struct hci_cp_le_add_to_resolv_list cp; + + cp.bdaddr_type = params->addr_type; +bacpy (&cp.bdaddr, ¶ms->addr); +memcpy (cp.peer_irk, irk->val,16 ); + +if (hci_dev_test_flag (hdev,HCI_PRIVACY )) +memcpy (cp.local_irk, hdev->irk,16 ); +else +memset (cp.local_irk,0 ,16 ); + +hci_req_add (req,HCI_OP_LE_ADD_TO_RESOLV_LIST , +sizeof (cp), &cp); + } + } +return 0 ; }
@@ -772,7 +809,7 @@ static u8 update_white_list(struct hci_request *req) }/* White list can not be used with RPAs */ -if (!allow_rpa && +if (!allow_rpa && !use_ll_privacy (hdev) &&hci_find_irk_by_addr (hdev, &b->bdaddr, b->bdaddr_type)) {return 0x00 ; }
Signature · 1 line
2.17.1
PATCH v3 4/8 Bluetooth: Translate additional address type during le_conn
In reply to Sathish NarasimmanWhen using controller based address resolution, then the new address types 0x02 and 0x03 are used. These types need to be converted back into either public address or random address types.
This patch is specially during LE_CREATE_CONN if using own_add_type as 0x02 or 0x03.
--- net/bluetooth/hci_event.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
net/bluetooth/hci_event.c +16 -0
@@ -2296,6 +2296,22 @@ static void cs_le_create_conn(struct hci_dev *hdev, bdaddr_t *peer_addr,if (!conn)return ; +/* When using controller based address resolution, then the new +* address types 0x02 and 0x03 are used. These types need to be +* converted back into either public address or random address type +*/ +if (use_ll_privacy (hdev) && +hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION )) { +switch (own_address_type) { +case ADDR_LE_DEV_PUBLIC_RESOLVED : + own_address_type =ADDR_LE_DEV_PUBLIC ; +break ; +case ADDR_LE_DEV_RANDOM_RESOLVED : + own_address_type =ADDR_LE_DEV_RANDOM ; +break ; + } + } +/* Store the initiator and responder address information which * is needed for SMP. These values will not change during the * lifetime of the connection.
Signature · 1 line
2.17.1
PATCH v3 5/8 Bluetooth: Let controller creates RPA during le create conn
In reply to Sathish NarasimmanWhen address resolution is enabled and set_privacy is enabled let's use own address type as 0x03
--- net/bluetooth/hci_request.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
net/bluetooth/hci_request.c +7 -1
@@ -2200,7 +2200,13 @@ int hci_update_random_address(struct hci_request *req, bool require_privacy,if (use_rpa) {int to; - *own_addr_type =ADDR_LE_DEV_RANDOM ; +/* If Controller supports LL Privacy use own address type is +* 0x03 +*/ +if (use_ll_privacy (hdev)) + *own_addr_type =ADDR_LE_DEV_RANDOM_RESOLVED ; +else + *own_addr_type =ADDR_LE_DEV_RANDOM ;if (!hci_dev_test_and_clear_flag (hdev,HCI_RPA_EXPIRED ) && !bacmp (&hdev->random_addr, &hdev->rpa))
Signature · 1 line
2.17.1
PATCH v3 6/8 Bluetooth: Enable/Disable address resolution during le create conn
In reply to Sathish NarasimmanIn this patch if le_create_conn process is started restrict to disable address resolution and same is disabled during le_enh_connection_complete
--- net/bluetooth/hci_conn.c | 7 +++++- net/bluetooth/hci_event.c | 4 ++++ net/bluetooth/hci_request.c | 45 ++++++++++++++++++++++++++++--------- net/bluetooth/hci_request.h | 3 ++- net/bluetooth/mgmt.c | 2 +- 5 files changed, 47 insertions(+), 14 deletions(-)
net/bluetooth/hci_conn.c +6 -1
@@ -1003,6 +1003,11 @@ struct hci_conn *hci_connect_le(struct hci_dev *hdev, bdaddr_t *dst,struct hci_request req;int err; +/* This ensures that during disable le_scan address resolution +* will not be disabled if it is followed by le_create_conn +*/ +bool rpa_le_conn = true; +/* Let's make sure that le is enabled.*/ if (!hci_dev_test_flag (hdev,HCI_LE_ENABLED )) {if (lmp_le_capable (hdev))
@@ -1103,7 +1108,7 @@ struct hci_conn *hci_connect_le(struct hci_dev *hdev, bdaddr_t *dst,* state. */ if (hci_dev_test_flag (hdev,HCI_LE_SCAN )) { -hci_req_add_le_scan_disable (&req); +hci_req_add_le_scan_disable (&req, rpa_le_conn);hci_dev_set_flag (hdev,HCI_LE_SCAN_INTERRUPTED ); }
net/bluetooth/hci_event.c +4 -0
@@ -5221,6 +5221,10 @@ static void hci_le_enh_conn_complete_evt(struct hci_dev *hdev,le16_to_cpu (ev->interval),le16_to_cpu (ev->latency), le16_to_cpu(ev->supervision_timeout)); + +if (use_ll_privacy (hdev) && +hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION )) +hci_req_disable_address_resolution (hdev); }static void hci_le_ext_adv_term_evt (struct hci_dev *hdev,struct sk_buff *skb)
net/bluetooth/hci_request.c +34 -11
118 lines not on this page · raw message
net/bluetooth/hci_request.h +2 -1
@@ -65,11 +65,12 @@ void __hci_req_write_fast_connectable(struct hci_request *req, bool enable);void __hci_req_update_name (struct hci_request *req);void __hci_req_update_eir (struct hci_request *req); -void hci_req_add_le_scan_disable (struct hci_request *req); +void hci_req_add_le_scan_disable (struct hci_request *req,bool rpa_le_conn);void hci_req_add_le_passive_scan (struct hci_request *req);void hci_req_prepare_suspend (struct hci_dev *hdev,enum suspended_state next); +void hci_req_disable_address_resolution (struct hci_dev *hdev);void hci_req_reenable_advertising (struct hci_dev *hdev);void __hci_req_enable_advertising (struct hci_request *req);void __hci_req_disable_advertising (struct hci_request *req);
net/bluetooth/mgmt.c +1 -1
@@ -5205,7 +5205,7 @@ static int set_scan_params(struct sock *sk, struct hci_dev *hdev,hci_req_init (&req, hdev); -hci_req_add_le_scan_disable (&req); +hci_req_add_le_scan_disable (&req, false);hci_req_add_le_passive_scan (&req);hci_req_run (&req,NULL );
Signature · 1 line
2.17.1
PATCH v3 7/8 Bluetooth: Enable RPA Timeout
In reply to Sathish NarasimmanEnable RPA timeout during bluetooth initialization. The RPA timeout value is used from hdev, which initialized from debug_fs
--- include/net/bluetooth/hci.h | 2 ++ net/bluetooth/hci_core.c | 8 ++++++++ 2 files changed, 10 insertions(+)
include/net/bluetooth/hci.h +2 -0
@@ -1637,6 +1637,8 @@ struct hci_rp_le_read_resolv_list_size {#define HCI_OP_LE_SET_ADDR_RESOLV_ENABLE 0x202d +#define HCI_OP_LE_SET_RPA_TIMEOUT 0x202e +#define HCI_OP_LE_READ_MAX_DATA_LEN 0x202fstruct hci_rp_le_read_max_data_len {__u8 status;
net/bluetooth/hci_core.c +8 -0
@@ -762,6 +762,14 @@ static int hci_init3_req(struct hci_request *req, unsigned long opt)hci_req_add (req,HCI_OP_LE_CLEAR_RESOLV_LIST ,0 ,NULL ); } +if (hdev->commands[35 ] &0x40 ) { +__le16 rpa_timeout =cpu_to_le16 (hdev->rpa_timeout); + +/* Set RPA timeout */ +hci_req_add (req,HCI_OP_LE_SET_RPA_TIMEOUT ,2 , + &rpa_timeout); + } +if (hdev->le_features[0 ] &HCI_LE_DATA_LEN_EXT ) {/* Read LE Maximum Data Length */ hci_req_add (req,HCI_OP_LE_READ_MAX_DATA_LEN ,0 ,NULL );
Signature · 1 line
2.17.1
PATCH v3 8/8 Bluetooth: Add support to enable LL PRIVACY using set_privacy
In reply to Sathish NarasimmanEnable LL Privacy using mgmt set_privacy command. The privacy value 0x03 is used here to enable LL Privacy.
Still to use LL Privacy controller support is must.
--- include/net/bluetooth/hci.h | 1 + net/bluetooth/hci_event.c | 6 ++++-- net/bluetooth/hci_request.c | 15 ++++++++++----- net/bluetooth/mgmt.c | 6 +++++- 4 files changed, 20 insertions(+), 8 deletions(-)
include/net/bluetooth/hci.h +1 -0
@@ -286,6 +286,7 @@ enum {HCI_SC_ONLY ,HCI_PRIVACY ,HCI_LIMITED_PRIVACY , +HCI_ENABLE_LL_PRIVACY ,HCI_RPA_EXPIRED ,HCI_RPA_RESOLVING , HCI_HS_ENABLED,
net/bluetooth/hci_event.c +4 -2
@@ -2301,7 +2301,8 @@ static void cs_le_create_conn(struct hci_dev *hdev, bdaddr_t *peer_addr,* converted back into either public address or random address type */ if (use_ll_privacy (hdev) && -hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION )) { +hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION ) && +hci_dev_test_flag (hdev,HCI_ENABLE_LL_PRIVACY )) {switch (own_address_type) {case ADDR_LE_DEV_PUBLIC_RESOLVED : own_address_type =ADDR_LE_DEV_PUBLIC ;
@@ -5223,7 +5224,8 @@ static void hci_le_enh_conn_complete_evt(struct hci_dev *hdev, le16_to_cpu(ev->supervision_timeout));if (use_ll_privacy (hdev) && -hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION )) +hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION ) && +hci_dev_test_flag (hdev,HCI_ENABLE_LL_PRIVACY ))hci_req_disable_address_resolution (hdev); }
net/bluetooth/hci_request.c +10 -5
@@ -678,7 +678,8 @@ void hci_req_add_le_scan_disable(struct hci_request *req, bool rpa_le_conn)/* Disable address resolution */ if (use_ll_privacy (hdev) && -hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION ) && !rpa_le_conn) { +hci_dev_test_flag (hdev,HCI_LL_RPA_RESOLUTION ) && !rpa_le_conn && +hci_dev_test_flag (hdev,HCI_ENABLE_LL_PRIVACY )) {__u8 enable =0x00 ;hci_req_add (req,HCI_OP_LE_SET_ADDR_RESOLV_ENABLE ,1 , &enable); }
@@ -696,7 +697,8 @@ static void del_from_white_list(struct hci_request *req, bdaddr_t *bdaddr, cp.bdaddr_type);hci_req_add (req,HCI_OP_LE_DEL_FROM_WHITE_LIST ,sizeof (cp), &cp); -if (use_ll_privacy (req->hdev)) { +if (use_ll_privacy (req->hdev) && +hci_dev_test_flag (req->hdev,HCI_ENABLE_LL_PRIVACY )) {struct smp_irk *irk; irk =hci_find_irk_by_addr (req->hdev, bdaddr, bdaddr_type);
@@ -748,7 +750,8 @@ static int add_to_white_list(struct hci_request *req, cp.bdaddr_type);hci_req_add (req,HCI_OP_LE_ADD_TO_WHITE_LIST ,sizeof (cp), &cp); -if (use_ll_privacy (hdev)) { +if (use_ll_privacy (hdev) && +hci_dev_test_flag (hdev,HCI_ENABLE_LL_PRIVACY )) {struct smp_irk *irk; irk = hci_find_irk_by_addr(hdev, ¶ms->addr,
@@ -869,7 +872,8 @@ static void hci_req_start_scan(struct hci_request *req, u8 type, u16 interval,return ; } -if (use_ll_privacy (hdev) && addr_resolv) { +if (use_ll_privacy (hdev) && addr_resolv && +hci_dev_test_flag (hdev,HCI_ENABLE_LL_PRIVACY )) {u8 enable =0x01 ;hci_req_add (req,HCI_OP_LE_SET_ADDR_RESOLV_ENABLE ,1 , &enable); }
@@ -2226,7 +2230,8 @@ int hci_update_random_address(struct hci_request *req, bool require_privacy,/* If Controller supports LL Privacy use own address type is * 0x03 */ -if (use_ll_privacy (hdev)) +if (use_ll_privacy (hdev) && +hci_dev_test_flag (hdev,HCI_ENABLE_LL_PRIVACY )) *own_addr_type =ADDR_LE_DEV_RANDOM_RESOLVED ;else *own_addr_type =ADDR_LE_DEV_RANDOM ;
net/bluetooth/mgmt.c +5 -1
@@ -5652,7 +5652,8 @@ static int set_privacy(struct sock *sk, struct hci_dev *hdev, void *cp_data,return mgmt_cmd_status (sk, hdev->id,MGMT_OP_SET_PRIVACY ,MGMT_STATUS_NOT_SUPPORTED ); -if (cp->privacy !=0x00 && cp->privacy !=0x01 && cp->privacy !=0x02 ) +if (cp->privacy !=0x00 && cp->privacy !=0x01 && cp->privacy !=0x02 + && cp->privacy !=0x03 )return mgmt_cmd_status (sk, hdev->id,MGMT_OP_SET_PRIVACY ,MGMT_STATUS_INVALID_PARAMS );
@@ -5674,6 +5675,8 @@ static int set_privacy(struct sock *sk, struct hci_dev *hdev, void *cp_data,hci_adv_instances_set_rpa_expired (hdev, true);if (cp->privacy ==0x02 )hci_dev_set_flag (hdev,HCI_LIMITED_PRIVACY ); +else if (cp->privacy ==0x03 ) +hci_dev_set_flag (hdev,HCI_ENABLE_LL_PRIVACY );else hci_dev_clear_flag (hdev,HCI_LIMITED_PRIVACY ); }else {
@@ -5682,6 +5685,7 @@ static int set_privacy(struct sock *sk, struct hci_dev *hdev, void *cp_data,hci_dev_clear_flag (hdev,HCI_RPA_EXPIRED );hci_adv_instances_set_rpa_expired (hdev, false);hci_dev_clear_flag (hdev,HCI_LIMITED_PRIVACY ); +hci_dev_clear_flag (hdev,HCI_ENABLE_LL_PRIVACY ); } err =send_settings_rsp (sk,MGMT_OP_SET_PRIVACY , hdev);
Signature · 1 line
2.17.1
Marcel Holtmann
maintainerRe: [PATCH v3 8/8] Bluetooth: Add support to enable LL PRIVACY using set_privacy
Hi Sathish,
Quoted 3 lines
Enable LL Privacy using mgmt
set_privacycommand. The privacy value0x03is used here to enable LL Privacy.
Still to use LL Privacy controller support is must.
that is not what I meant. And it is also misleading since Set Privacy is enabling RPA usage and not RPA resolution. So what I meant was using the Set Experimental Features mgmt command to enable usage of RPA resolution in the controller.
Regards
Marcel
Re: [PATCH v3 8/8] Bluetooth: Add support to enable LL PRIVACY using set_privacy
Hi Marcel
Quoted 8 lines · Marcel Holtmann
Hi Sathish,
Quoted 3 lines
Enable LL Privacy using mgmt
set_privacycommand. The privacy value0x03is used here to enable LL Privacy.
Still to use LL Privacy controller support is must.that is not what I meant. And it is also misleading since Set Privacy is enabling RPA usage and not RPA resolution. So what I meant was using the Set Experimental Features mgmt command to enable usage of RPA resolution in the controller.
Updated v4 of the patches
Please review them
Quoted 5 lines
Regards
Marcel
Regards
Sathish N