Bluetooth: controller: Make must-expire runtime configurable
Under CONFIG_BT_TICKER_EXT configuration, the ticker interface has been extended to support enabling/disabling must-expire scheduling. This means that conn and slave ticker start calls can now omit must-expire default-on configuration, relying on LLL updating the mode as needed. Signed-off-by: Morten Priess <mtpr@oticon.com>
This commit is contained in:
parent
f234c5f876
commit
467fd155a8
4 changed files with 71 additions and 19 deletions
|
@ -2474,11 +2474,11 @@ static inline int event_conn_upd_prep(struct ll_conn *conn, uint16_t lazy,
|
|||
ticks_at_expire, ticks_win_offset,
|
||||
HAL_TICKER_US_TO_TICKS(periodic_us),
|
||||
HAL_TICKER_REMAINDER(periodic_us),
|
||||
#if defined(CONFIG_BT_CTLR_CONN_META)
|
||||
TICKER_LAZY_MUST_EXPIRE,
|
||||
#else
|
||||
#if defined(CONFIG_BT_TICKER_COMPATIBILITY_MODE)
|
||||
TICKER_NULL_LAZY,
|
||||
#endif /* CONFIG_BT_CTLR_CONN_META */
|
||||
#else
|
||||
TICKER_LAZY_MUST_EXPIRE_KEEP,
|
||||
#endif
|
||||
(ticks_slot_overhead +
|
||||
conn->evt.ticks_slot),
|
||||
#if defined(CONFIG_BT_PERIPHERAL) && defined(CONFIG_BT_CENTRAL)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue