Bluetooth: Kconfig: Make ACL buffer count ranges more reasonable
We need at least 2 buffers in each direction in case of fragmentation, and there's no need to have such a low maximum count. Change-Id: Ie25f4ebb231176a855e9651cb896fa8b59279629 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
db946d8bae
commit
fa5dfa1366
1 changed files with 2 additions and 2 deletions
|
@ -90,7 +90,7 @@ if BLUETOOTH_CONN
|
|||
config BLUETOOTH_ACL_IN_COUNT
|
||||
int "Number of incoming ACL data buffers"
|
||||
default 5
|
||||
range 1 16
|
||||
range 2 64
|
||||
help
|
||||
Number of buffers available for incoming ACL data.
|
||||
|
||||
|
@ -106,7 +106,7 @@ config BLUETOOTH_ACL_IN_SIZE
|
|||
config BLUETOOTH_ACL_OUT_COUNT
|
||||
int "Number of incoming ACL data buffers"
|
||||
default 5
|
||||
range 1 16
|
||||
range 2 64
|
||||
help
|
||||
Number of buffers available for incoming ACL data.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue