:orphan:

.. title:: CONFIG_BT_CTLR_CONN_RANDOM_FORCE

.. kconfig:: CONFIG_BT_CTLR_CONN_RANDOM_FORCE

CONFIG_BT_CTLR_CONN_RANDOM_FORCE
################################

*Enable random forced scheduling for peripheral on missed anchor point*

Type: ``bool``

Help
====

.. code-block:: none

    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
===================

\ :kconfig:`BT_PERIPHERAL <CONFIG_BT_PERIPHERAL>` && \ :kconfig:`BT_CONN <CONFIG_BT_CONN>` && \ :kconfig:`BT_LL_SW_SPLIT <CONFIG_BT_LL_SW_SPLIT>` && \ :kconfig:`BT_CTLR <CONFIG_BT_CTLR>` && \ :kconfig:`BT_HCI <CONFIG_BT_HCI>` && \ :kconfig:`BT <CONFIG_BT>`

*(Includes any dependencies from ifs and menus.)*

Default
=======

- y

Kconfig definition
==================



At ``<Zephyr Subsystem>/bluetooth/controller/Kconfig.ll_sw_split:503``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``<Zephyr Subsystem>/Kconfig:9`` → ``<Zephyr Subsystem>/bluetooth/Kconfig:175`` → ``<Zephyr Subsystem>/bluetooth/controller/Kconfig:659``

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

.. code-block:: kconfig

    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.)*