Bluetooth: controller: Replace slave with peripheral

Replace the old slave term with the new peripheral
one from the Bluetooth spec v5.3.

Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
This commit is contained in:
Carles Cufi 2021-09-20 16:25:06 +02:00 committed by Carles Cufí
commit 947b38ac0a
40 changed files with 315 additions and 309 deletions

View file

@ -18,7 +18,7 @@ config BT_LLL_VENDOR_NORDIC
!BT_CTLR_PHY_2M_NRF
select BT_CTLR_CONN_PARAM_REQ_SUPPORT
select BT_CTLR_EXT_REJ_IND_SUPPORT
select BT_CTLR_SLAVE_FEAT_REQ_SUPPORT
select BT_CTLR_PER_INIT_FEAT_XCHG_SUPPORT
select BT_CTLR_DATA_LEN_UPDATE_SUPPORT if HAS_HW_NRF_CCM_LFLEN_8BIT || \
BT_CTLR_DATA_LENGTH_CLEAR
select BT_CTLR_PRIVACY_SUPPORT if !SOC_SERIES_NRF51X
@ -307,15 +307,15 @@ config BT_CTLR_SCHED_ADVANCED
depends on (BT_MAX_CONN != 0) && BT_CTLR_SCHED_ADVANCED_SUPPORT
default y if !(BT_PERIPHERAL && !BT_CENTRAL)
help
Enable non-overlapping placement of observer, initiator and master
Enable non-overlapping placement of observer, initiator and central
roles in timespace. Uses window offset in connection updates and uses
connection parameter request in slave role to negotiate
non-overlapping placement with active master roles to avoid slave
roles drifting into active master roles in the local controller.
connection parameter request in peripheral role to negotiate
non-overlapping placement with active central roles to avoid peripheral
roles drifting into active central roles in the local controller.
This feature maximizes the average data transmission amongst active
concurrent master and slave connections while other observer,
initiator, master or slave roles are active in the local controller.
concurrent central and peripheral connections while other observer,
initiator, central or peripheral roles are active in the local controller.
Disabling this feature will lead to overlapping role in timespace
leading to skipped events amongst active roles.