Help¶

Enforce flow control rules on incoming PDUs, preventing a peer from sending new requests until a previous one has been responded or sending a new indication until a previous one has been confirmed. This may need to be disabled to avoid potential race conditions arising from a USB based HCI transport that splits HCI events and ACL data to separate endpoints.

Direct dependencies¶

BT_CONN && BT_HCI_HOST && BT_HCI && BT

(Includes any dependencies from if’s and menus.)

Defaults¶

“y” if !(BOARD_QEMU_CORTEX_M3 || BOARD_QEMU_X86 || BOARD_NATIVE_POSIX) && BT_CONN && BT_HCI_HOST && BT_HCI && BT

Kconfig definition¶

At subsys/bluetooth/host/Kconfig:216

Included via Kconfig:10 → Kconfig.zephyr:35 → subsys/Kconfig:8 → subsys/bluetooth/Kconfig:155

Menu path: (top menu) → Bluetooth

config BT_ATT_ENFORCE_FLOW
    bool
    prompt "Enforce strict flow control semantics for incoming PDUs" if BT_CONN && BT_HCI_HOST && BT_HCI && BT
    default "y" if !(BOARD_QEMU_CORTEX_M3 || BOARD_QEMU_X86 || BOARD_NATIVE_POSIX) && BT_CONN && BT_HCI_HOST && BT_HCI && BT
    depends on BT_CONN && BT_HCI_HOST && BT_HCI && BT
    help
      Enforce flow control rules on incoming PDUs, preventing a peer
      from sending new requests until a previous one has been responded
      or sending a new indication until a previous one has been
      confirmed. This may need to be disabled to avoid potential race
      conditions arising from a USB based HCI transport that splits
      HCI events and ACL data to separate endpoints.

(Definitions include propagated dependencies, including from if’s and menus.)