Bluetooth: Make Kconfig buffer sizes follow MTU sizes
It's more intuitive to specify needed MTU sizes instead of raw buffer sizes. The exact buffer size calculations can instead be made internally in the code (using the BT_L2CAP_BUF_SIZE helper macro). Change-Id: I0637340a7d99e04020f57f49ecd8e6dcfcc4bcf4 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
50256ea514
commit
8167ababe0
6 changed files with 26 additions and 28 deletions
|
@ -94,14 +94,22 @@ config BLUETOOTH_ACL_IN_COUNT
|
|||
help
|
||||
Number of buffers available for incoming ACL data.
|
||||
|
||||
config BLUETOOTH_ACL_IN_SIZE
|
||||
int "Size of incoming ACL data buffers"
|
||||
default 74 if BLUETOOTH_SMP
|
||||
default 32 if !BLUETOOTH_SMP
|
||||
range 74 1300 if BLUETOOTH_SMP
|
||||
range 32 1300 if !BLUETOOTH_SMP
|
||||
config BLUETOOTH_L2CAP_IN_MTU
|
||||
int "Maximum supported L2CAP MTU for incoming data"
|
||||
default 65 if BLUETOOTH_SMP
|
||||
default 23 if !BLUETOOTH_SMP
|
||||
range 65 1300 if BLUETOOTH_SMP
|
||||
range 23 1300 if !BLUETOOTH_SMP
|
||||
help
|
||||
Maximum size of each incoming ACL data buffer.
|
||||
Maximum size of each incoming L2CAP PDU.
|
||||
|
||||
config BLUETOOTH_ATT_MTU
|
||||
int "Attribute Protocol (ATT) channel MTU"
|
||||
default 23
|
||||
range 23 BLUETOOTH_L2CAP_IN_MTU
|
||||
help
|
||||
The MTU for the ATT channel. The minimum and default is 23,
|
||||
whereas the maximum is limited by CONFIG_BLUETOOTH_L2CAP_IN_MTU.
|
||||
endif # BLUETOOTH_CONN
|
||||
|
||||
if BLUETOOTH_PERIPHERAL || BLUETOOTH_CENTRAL
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue