Searched refs:CCC (Results 1 – 17 of 17) sorted by relevance
30 CCC, enumerator62 subscribe_params.ccc_handle = gatt_handles[CCC]; in subscribe()113 gatt_handles[CCC] = attr->handle; in discover_func()139 LOG_DBG("ccc handle: %d", gatt_handles[CCC]); in gatt_discover()
78 forgot the CCC values and sets them again. If this behavior is not198 bool "Support to automatic discover the CCC handles of characteristics"201 This option enables support for GATT to initiate discovery for CCC202 handles if the CCC handle is unknown by the application.
218 bool "Load CCC values from settings when peer connects"224 Disabling this option will increase memory usage as CCC values for all231 Triggers the storage of the CF and CCC right after a write.243 bool "Store CCC value immediately after it has been written"249 been updated. If the option is disabled, the CCC is only stored on273 int "Max number of Client Characteristic Configuration (CCC)"277 Defines the max number of Client Characteristic Configuration (CCC)
24 The I3C shell supports info, bus recovery, CCC, I3C read and
349 by default. Storing CCC right after it's written reduces risk of350 inconsistency of CCC values between bonded peers363 * Added storing of the CCC data upon paring complete1107 * :github:`40759` - Bluetooth: host: Improper restore of CCC values and handling Service Change ind…1108 * :github:`40758` - Bluetooth: host: CCC values are not immediately stored on GATT Server by defaul…1187 * :github:`39989` - Zephyr does not persist CCC data written before bonding when bonding has comple…
376 * GATT: Added an initializer for GATT CCC structures378 * Added ability to load CCC settings on demand to reduce memory usage598 * :github:`20299` - bluetooth: host: Connection not being unreferenced when using CCC match callback
691 * The application can now request for the CCC descriptor to be discovered705 * Fixed CCC restoring when using settings lazy loading.708 * GATT no longer assumes the position of the CCC descriptor and instead1294 * :github:`26862` - Bluetooth: GATT: CCC is not properly stored1643 * :github:`23961` - CCC does not get cleared when CONFIG_BT_KEYS_OVERWRITE_OLDEST is enabled
579 * :github:`18547` - Bluetooth: GATT: Fix using variable size storage for CCC710 * :github:`18188` - [zephyr 1.14] Re-enabling CCC gets broken when used along with Robust Caching976 * :github:`16734` - Bluetooth: GATT: Writing 1 byte to a CCC access invalid memory1244 * :github:`15508` - No space to store CCC cfg
210 * settings-based persistent storage functionality for BLE (including CCC) and221 * GATT CCC handling fixes
147 * :github:`16734` - Bluetooth: GATT: Writing 1 byte to a CCC access invalid memory232 * :github:`20299` - bluetooth: host: Connection not being unreferenced when using CCC match callback347 * :github:`16734` - Bluetooth: GATT: Writing 1 byte to a CCC access invalid memory2054 * :github:`10460` - Bluetooth: settings: No space to store CCC config after successful pairing2074 * :github:`10312` - Bluetooth: settings: CCC not stored on device reset
751 * :github:`23023` - Bluetooth: GATT CCC problem (GATT Server)837 * :github:`22514` - Bluetooth: gatt: CCC cfg not flushed if device was previously paired
1560 * :github:`29150` - CONFIG_BT_SETTINGS_CCC_LAZY_LOADING never loads CCC1935 * :github:`10460` - Bluetooth: settings: No space to store CCC config after successful pairing
1080 * :github:`23961` - CCC does not get cleared when CONFIG_BT_KEYS_OVERWRITE_OLDEST is enabled
2827 - :github:`54770` - Bluetooth: GATT: CCC and CF values written by privacy-disabled peer before bond…2856 * :github:`54770` - Bluetooth: GATT: CCC and CF values written by privacy-disabled peer before bond…
910 * Added shell support for querying bus and CCC commands.
1074 * :github:`35876` - Bluetooth: host: CCC store not correctly handled for multiple connections
2219 * :github:`47682` - bt_gatt_unsubscribe creates write request to CCC and then cancels it
