Bluetooth: Use event/cmd lengths instead of buffer sizes in KConfig
It's more intuitive to specify needed command or event lengths rather than the raw buffer size in Kconfig. The exact buffer size calculation can be done in the code itself. Change-Id: I2760cc1182a689b26405e4c2b1428f140b4aa88a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
8167ababe0
commit
3bc43254e0
2 changed files with 22 additions and 14 deletions
|
@ -62,12 +62,12 @@ config BLUETOOTH_HCI_CMD_COUNT
|
|||
help
|
||||
Number of buffers available for HCI commands.
|
||||
|
||||
config BLUETOOTH_HCI_CMD_SIZE
|
||||
int "Size of HCI command buffers"
|
||||
default 68
|
||||
range 68 260
|
||||
config BLUETOOTH_MAX_CMD_LEN
|
||||
int "Maximum supported HCI command length"
|
||||
default 64
|
||||
range 64 255
|
||||
help
|
||||
Maximum size of each HCI command buffer.
|
||||
Maximum length of each HCI command.
|
||||
|
||||
config BLUETOOTH_HCI_EVT_COUNT
|
||||
int "Number of HCI event buffers"
|
||||
|
@ -79,12 +79,15 @@ config BLUETOOTH_HCI_EVT_COUNT
|
|||
sure we've got enough buffers to handle bursts of Number of
|
||||
Completed Packets HCI events.
|
||||
|
||||
config BLUETOOTH_HCI_EVT_SIZE
|
||||
int "Size of HCI event buffers"
|
||||
default 72
|
||||
range 72 260
|
||||
config BLUETOOTH_MAX_EVT_LEN
|
||||
int "Maximum supported HCI event length"
|
||||
default 68
|
||||
range 68 255
|
||||
help
|
||||
Maximum size of each HCI event buffer.
|
||||
Maximum size of each HCI event buffer. E.g. one big event
|
||||
for LE is the Command Complete for Read Local Supported
|
||||
Commands. It is a 3 byte Command Complete header + 65 byte
|
||||
return parameters = 68 bytes in total.
|
||||
|
||||
if BLUETOOTH_CONN
|
||||
config BLUETOOTH_ACL_IN_COUNT
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue