Bluetooth: controller: Fix CONFIG_BT_CTLR_TX_BUFFER_SIZE range
Fix CONFIG_BT_CTLR_TX_BUFFER_SIZE value range to 251 Bytes due to implementation limitation in use of u8_t for PDU length fields in controller Tx buffers. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
This commit is contained in:
parent
8cd9a94b2f
commit
51c46d94ed
1 changed files with 3 additions and 3 deletions
|
@ -227,15 +227,15 @@ config BT_CTLR_TX_BUFFERS
|
||||||
|
|
||||||
config BT_CTLR_TX_BUFFER_SIZE
|
config BT_CTLR_TX_BUFFER_SIZE
|
||||||
int "Tx buffer size"
|
int "Tx buffer size"
|
||||||
range 27 16384
|
range 27 251
|
||||||
default 27
|
default 27
|
||||||
help
|
help
|
||||||
Size of the Tx buffers and the value returned in HCI LE Read Buffer
|
Size of the Tx buffers and the value returned in HCI LE Read Buffer
|
||||||
Size command response. If this size if greater than effective PDU size
|
Size command response. If this size if greater than effective PDU size
|
||||||
then controller will perform fragmentation before transmitting on the
|
then controller will perform fragmentation before transmitting on the
|
||||||
the packet on air.
|
the packet on air.
|
||||||
Maximum is set to 16384 due to implementation limitations (use of
|
Maximum is set to 251 due to implementation limitations (use of
|
||||||
u16_t for size/length variables).
|
u8_t for length field in PDU buffer structure).
|
||||||
|
|
||||||
choice
|
choice
|
||||||
prompt "Tx Power"
|
prompt "Tx Power"
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue