michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: settings: store CCC on write

Browse source 
By default, CCC value is only stored to persistent memory during
BT disconnection. This commit adds an optional storing of CCC right
after it has been updated. This results in better robustness of
peripheral but increases system workqueue stack usage.

Signed-off-by: Filip Kubicz <filip.kubicz@nordicsemi.no>
This commit is contained in:
Filip Kubicz 2018-10-08 14:33:40 +02:00 • committed by Johan Hedberg
commit 7c290b053d
2 changed files with 94 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

16
subsys/bluetooth/host/Kconfig
View file

@ -101,7 +101,7 @@ config BT_RX_STACK_SIZE
depends on BT_HCI_HOST || BT_RECV_IS_RX_THREAD
default 512 if BT_HCI_RAW
default 2048 if BT_MESH
default 2048 if BT_SETTINGS
default 2200 if BT_SETTINGS
default 1024
range 512 65536 if BT_HCI_RAW
range 1100 65536 if BT_MESH
@ -153,6 +153,20 @@ config BT_SETTINGS
which case it's more efficient to load all settings in one go,
instead of each subsystem doing it independently.
if BT_SETTINGS
config BT_SETTINGS_CCC_STORE_ON_WRITE
bool "Store CCC value immediately after it has been written"
default n
help
Store Client Configuration Characteristic value right after it has
been updated.
By default, CCC is only stored on disconnection.
Choosing this option is safer for battery-powered devices or devices
that expect to be reset suddenly. However, it requires additional
workqueue stack space.
endif # BT_SETTINGS
if BT_CONN
if BT_HCI_ACL_FLOW_CONTROL