michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: Mesh: Kconfig: Tweak RX SDU value

Browse source 
Update the RX SDU Kconfig value to something that reflects better
current use cases and doesn't waste memory needlessly. Also lower the
minimum to two segments, since while many samples need three for their
composition data (typically the biggest transferred payload), it's
possible to have a very simple node whose composition fits in two
segments.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
Johan Hedberg 2018-07-25 15:39:02 +03:00 • committed by Johan Hedberg
commit c384631dac
1 changed files with 8 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

13
subsys/bluetooth/host/mesh/Kconfig
View file

@ -206,12 +206,15 @@ config BT_MESH_RX_SEG_MSG_COUNT
config BT_MESH_RX_SDU_MAX config BT_MESH_RX_SDU_MAX
int "Maximum incoming Upper Transport Access PDU length" int "Maximum incoming Upper Transport Access PDU length"
default 384 default 72
range 36 384 range 24 384
help help
Maximum incoming Upper Transport Access PDU length. Leave this Maximum incoming Upper Transport Access PDU length. This
to the default value, unless you really need to optimize memory determines also how many segments incoming segmented messages
usage. can have. Each segment can contain 12 bytes, so this value should
be set to a multiple of 12 to avoid wasted memory. The minimum
requirement is 2 segments (24 bytes) whereas the maximum supported
by the Mesh specification is 32 segments (384 bytes).
config BT_MESH_TX_SEG_MAX config BT_MESH_TX_SEG_MAX
int "Maximum number of segments in outgoing messages" int "Maximum number of segments in outgoing messages"