From 51c46d94ede8f71c197d3b5d71d6aa6ebb0723a7 Mon Sep 17 00:00:00 2001 From: Vinayak Kariappa Chettimada Date: Tue, 14 Jan 2020 19:18:23 +0530 Subject: [PATCH] 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 --- subsys/bluetooth/controller/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/subsys/bluetooth/controller/Kconfig b/subsys/bluetooth/controller/Kconfig index 9880c4d8a39..0dc2322110c 100644 --- a/subsys/bluetooth/controller/Kconfig +++ b/subsys/bluetooth/controller/Kconfig @@ -227,15 +227,15 @@ config BT_CTLR_TX_BUFFERS config BT_CTLR_TX_BUFFER_SIZE int "Tx buffer size" - range 27 16384 + range 27 251 default 27 help 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 then controller will perform fragmentation before transmitting on the the packet on air. - Maximum is set to 16384 due to implementation limitations (use of - u16_t for size/length variables). + Maximum is set to 251 due to implementation limitations (use of + u8_t for length field in PDU buffer structure). choice prompt "Tx Power"