gap: document requirement for RPA in extended advertising

This commit is contained in:
Matthias Ringwald 2024-01-17 11:49:54 +01:00
parent 67bf59ff2b
commit 64e2b019f2
2 changed files with 3 additions and 0 deletions

View File

@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
## Unreleased
### Added
### Fixed
- GAP: allow use of own address type different from gap_random_set_mode() incl. RPA in LE Extended Advertising
- HFP HF: send HF Indicator update only if enabled by AG
- SM: abort pairing with invalid parameter error for encryption key size > 16
### Changed

View File

@ -681,6 +681,7 @@ uint8_t gap_extended_advertising_set_resolvable_private_address_update(uint16_t
/**
* @brief Provide storage for new advertising set and setup on Controller
* @note Using RPA as own_address_type requires ENABLE_LE_ENHANCED_CONNECTION_COMPLETE_EVENT is required for pairing
* @param storage to use by stack, needs to stay valid until adv set is removed with gap_extended_advertising_remove
* @param advertising_parameters
* @param out_advertising_handle to use with other adv config commands
@ -691,6 +692,7 @@ uint8_t gap_extended_advertising_setup(le_advertising_set_t * storage, const le_
/**
* @param Set advertising params for advertising set
* @note Using RPA as own_address_type requires ENABLE_LE_ENHANCED_CONNECTION_COMPLETE_EVENT is required for pairing
* @param advertising_handle
* @param advertising_parameters
* @return status