:orphan: .. title:: BT_CTLR_SCHED_ADVANCED .. option:: CONFIG_BT_CTLR_SCHED_ADVANCED *Advanced scheduling* Type: ``bool`` Help ==== Enable non-overlapping placement of observer, initiator and master 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. 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. Disabling this feature will lead to overlapping role in timespace leading to skipped events amongst active roles. Direct dependencies =================== \ :option:`BT_MAX_CONN ` != 0 && \ :option:`BT_CTLR_SCHED_ADVANCED_SUPPORT ` && \ :option:`BT_LL_SW_SPLIT ` && \ :option:`BT_CTLR ` && \ :option:`BT_HCI ` && \ :option:`BT ` *(Includes any dependencies from ifs and menus.)* Default ======= - y if !(\ :option:`BT_PERIPHERAL ` && !\ :option:`BT_CENTRAL `) Kconfig definition ================== .. highlight:: kconfig At ``subsys/bluetooth/controller/Kconfig.ll_sw_split:262`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:9`` → ``subsys/bluetooth/Kconfig:240`` → ``subsys/bluetooth/controller/Kconfig:594`` Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Bluetooth Controller → Advanced features .. parsed-literal:: config BT_CTLR_SCHED_ADVANCED bool "Advanced scheduling" if \ :option:`BT_CTLR_ADVANCED_FEATURES ` default y if !(\ :option:`BT_PERIPHERAL ` && !\ :option:`BT_CENTRAL `) depends on \ :option:`BT_MAX_CONN ` != 0 && \ :option:`BT_CTLR_SCHED_ADVANCED_SUPPORT ` && \ :option:`BT_LL_SW_SPLIT ` && \ :option:`BT_CTLR ` && \ :option:`BT_HCI ` && \ :option:`BT ` help Enable non-overlapping placement of observer, initiator and master 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. 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. Disabling this feature will lead to overlapping role in timespace leading to skipped events amongst active roles. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*