michaelh/zephyr
1
0
Fork 0
Code Releases Activity

bluetooth: kconfig: Fix swapped 'range's on BT_RFCOMM_L2CAP_MTU

Browse source 
Whoever added Zephyr's prefer-later-defaults Kconfig patch originally
didn't do the same for 'range's. Earlier ranges are still preferred.
Swap the ranges on BT_RFCOMM_L2CAP_MTU to give the intended behavior.

Fixes the following warning for tests/bluetooth/shell/prj_br.conf:

  warning: default value 200 on BT_RFCOMM_L2CAP_MTU (defined at
  subsys/bluetooth/host/Kconfig:508) clamped to 264 due to being outside
  the active range ([264, 32767])

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
This commit is contained in:
Ulf Magnusson 2018-07-20 18:30:58 +02:00 • committed by Anas Nashif
commit 642db77591
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
subsys/bluetooth/host/Kconfig
View file

@ -524,8 +524,8 @@ config BT_RFCOMM_L2CAP_MTU
default BT_RX_BUF_LEN
default BT_L2CAP_RX_MTU if BT_HCI_ACL_FLOW_CONTROL
depends on BT_RFCOMM
range BT_RX_BUF_LEN 32767
range BT_L2CAP_RX_MTU 32767 if BT_HCI_ACL_FLOW_CONTROL
range BT_RX_BUF_LEN 32767
help
Maximum size of L2CAP PDU for RFCOMM frames.