Help¶

When enabled, controller will have legacy behavior and randomly force priority at next ticker scheduling for peripheral role, if anchor point is missed. Two or more connections with similar interval on a device connected to a peer device having two or more connections at its end with same interval could lock to a round robin pattern where in neither of the central nor peripheral event would be in sync at either end. Randomness allows to break this locked round robin pattern permitting an anchor point sync.

Direct dependencies¶

BT_PERIPHERAL && BT_CONN && BT_LL_SW_SPLIT && BT_CTLR && BT_HCI && BT

(Includes any dependencies from ifs and menus.)

Default¶

y

Kconfig definition¶

At <Zephyr>/subsys/bluetooth/controller/Kconfig.ll_sw_split:439

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:9 → <Zephyr>/subsys/bluetooth/Kconfig:240 → <Zephyr>/subsys/bluetooth/controller/Kconfig:595

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Bluetooth Controller → Advanced features

config BT_CTLR_CONN_RANDOM_FORCE
    bool "Enable random forced scheduling for peripheral on missed anchor point" if BT_CTLR_ADVANCED_FEATURES
    default y
    depends on BT_PERIPHERAL && BT_CONN && BT_LL_SW_SPLIT && BT_CTLR && BT_HCI && BT
    help
      When enabled, controller will have legacy behavior and randomly force
      priority at next ticker scheduling for peripheral role, if anchor point is
      missed.
      Two or more connections with similar interval on a device connected
      to a peer device having two or more connections at its end with same
      interval could lock to a round robin pattern where in neither of the central
      nor peripheral event would be in sync at either end. Randomness allows
      to break this locked round robin pattern permitting an anchor point sync.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)