58c5e32e08
Change doc of CONFIG_BT_PRIVACY to explicitly say it's needed for both generating and resolving RPAs. Disable host-based RPA resolution in `bt_conn_le_create` when !CONFIG_BT_PRIVACY. Update doc of `bt_conn_le_create` to document that CONFIG_BT_PRIVACY is a requirement for resolving RPAs. Also explictly say that this function will resolve private identities. Also explain the expected effect of Network Privacy on this function. Reduce coupling to `bt_le_create_conn_ext` and `bt_le_create_conn_legacy` in `bt_conn_le_create` by just use `resp_addr` when it's set, instead of "knowing" when it had been set. The alternative would be to also update `bt_le_create_conn_ext` and `bt_le_create_conn_legacy` to have `(IS_ENABLED(CONFIG_BT_PRIVACY) && (!bt_dev.le.rl_size || bt_dev.le.rl_entries > bt_dev.le.rl_size))` Signed-off-by: Aleksander Wasaznik <aleksander.wasaznik@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| zephyr | ||