:orphan:

.. title:: CONFIG_BT_CTLR_ADV_SYNC_PDU_BACK2BACK

.. kconfig:: CONFIG_BT_CTLR_ADV_SYNC_PDU_BACK2BACK

CONFIG_BT_CTLR_ADV_SYNC_PDU_BACK2BACK
#####################################

*Enable back-to-back transmission of periodic advertising trains*

Type: ``bool``

Help
====

.. code-block:: none

    Enables transmission of AUX_CHAIN_IND in periodic advertising train by
    sending each AUX_CHAIN_IND one after another back-to-back.
    Note, consecutive AUX_CHAIN_IND packets are not scheduled but sent at
    a constant offset on a best effort basis. This means advertising train can
    be preempted by other event at any time.

Direct dependencies
===================

\ :kconfig:`BT_CTLR_ADV_PERIODIC <CONFIG_BT_CTLR_ADV_PERIODIC>` && \ :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.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Symbols selected by this symbol
===============================

- \ :kconfig:`BT_CTLR_ADV_PDU_LINK <CONFIG_BT_CTLR_ADV_PDU_LINK>`

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



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

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_ADV_SYNC_PDU_BACK2BACK
    	bool "Enable back-to-back transmission of periodic advertising trains" if BT_CTLR_ADVANCED_FEATURES
    	select BT_CTLR_ADV_PDU_LINK
    	depends on BT_CTLR_ADV_PERIODIC && BT_LL_SW_SPLIT && BT_CTLR && BT_HCI && BT
    	help
    	  Enables transmission of AUX_CHAIN_IND in periodic advertising train by
    	  sending each AUX_CHAIN_IND one after another back-to-back.
    	  Note, consecutive AUX_CHAIN_IND packets are not scheduled but sent at
    	  a constant offset on a best effort basis. This means advertising train can
    	  be preempted by other event at any time.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*