-
CONFIG_BT_L2CAP_TX_FRAG_COUNT¶
Number of L2CAP TX fragment buffers
Type: int
Help¶
Number of buffers available for fragments of TX buffers. Warning: setting this to 0 means that the application must ensure that queued TX buffers never need to be fragmented, i.e. that the controller’s buffer size is large enough. If this is not ensured, and there are no dedicated fragment buffers, a deadlock may occur. In most cases the default value of 2 is a safe bet.
Direct dependencies¶
BT_CONN && BT_HCI_HOST && BT_HCI && BT
(Includes any dependencies from if’s and menus.)
Defaults¶
- 2 if
BT_CONN&&BT_HCI_HOST&&BT_HCI&&BT
Kconfig definition¶
At subsys/bluetooth/host/Kconfig:194
Included via Kconfig:10 → Kconfig.zephyr:39 → subsys/Kconfig:8 → subsys/bluetooth/Kconfig:144
Menu path: (top menu) → Bluetooth
config BT_L2CAP_TX_FRAG_COUNT
int
prompt "Number of L2CAP TX fragment buffers" if BT_CONN && BT_HCI_HOST && BT_HCI && BT
range 0 255 if BT_CONN && BT_HCI_HOST && BT_HCI && BT
default 2 if BT_CONN && BT_HCI_HOST && BT_HCI && BT
depends on BT_CONN && BT_HCI_HOST && BT_HCI && BT
help
Number of buffers available for fragments of TX buffers. Warning:
setting this to 0 means that the application must ensure that
queued TX buffers never need to be fragmented, i.e. that the
controller's buffer size is large enough. If this is not ensured,
and there are no dedicated fragment buffers, a deadlock may occur.
In most cases the default value of 2 is a safe bet.
(Definitions include propagated dependencies, including from if’s and menus.)