:orphan:

.. title:: BT_SETTINGS_CCC_STORE_ON_WRITE

.. option:: CONFIG_BT_SETTINGS_CCC_STORE_ON_WRITE

*Store CCC value immediately after it has been written*

Type: ``bool``

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.

Direct dependencies
===================

\ :option:`BT_SETTINGS <CONFIG_BT_SETTINGS>` && \ :option:`BT_HCI_HOST <CONFIG_BT_HCI_HOST>` && \ :option:`BT_HCI <CONFIG_BT_HCI>` && \ :option:`BT <CONFIG_BT>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definition
==================

.. highlight:: kconfig

At ``subsys/bluetooth/host/Kconfig:207``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:9`` → ``subsys/bluetooth/Kconfig:239``

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Store Bluetooth state and configuration persistently

.. parsed-literal::

    config BT_SETTINGS_CCC_STORE_ON_WRITE
    	bool "Store CCC value immediately after it has been written"
    	depends on \ :option:`BT_SETTINGS <CONFIG_BT_SETTINGS>` && \ :option:`BT_HCI_HOST <CONFIG_BT_HCI_HOST>` && \ :option:`BT_HCI <CONFIG_BT_HCI>` && \ :option:`BT <CONFIG_BT>`
    	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.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*