Home
last modified time | relevance | path

Searched refs:persist (Results 1 – 15 of 15) sorted by relevance

/Zephyr-Core-3.5.0/tests/bsim/bluetooth/host/adv/resume/src/
Dbs_bt_utils.h78 void advertise_connectable(int id, bool persist);
Dbs_bt_utils.c190 void advertise_connectable(int id, bool persist) in advertise_connectable() argument
199 param.options |= persist ? 0 : BT_LE_ADV_OPT_ONE_TIME; in advertise_connectable()
/Zephyr-Core-3.5.0/subsys/logging/backends/
DKconfig.swo33 debug probe. Such configuration will persist only until the device
/Zephyr-Core-3.5.0/drivers/sensor/isl29035/
DKconfig124 prompt "Interrupt persist cycles"
/Zephyr-Core-3.5.0/boards/riscv/neorv32/doc/
Dindex.rst161 The steps to persist the application within the FPGA bitstream are covered by
/Zephyr-Core-3.5.0/doc/services/retention/
Dindex.rst10 when a device reboots. The stored data should not persist in the event of a
/Zephyr-Core-3.5.0/boards/arm/arty/doc/
Dindex.rst184 The steps to persist the application within the FPGA bitstream are covered by
/Zephyr-Core-3.5.0/doc/services/settings/
Dindex.rst216 This is a simple example showing how to persist runtime state. In this example,
/Zephyr-Core-3.5.0/boards/arm/cc3235sf_launchxl/doc/
Dindex.rst184 which prepends a debug header enabling the flash to persist over
/Zephyr-Core-3.5.0/boards/arm/cc3220sf_launchxl/doc/
Dindex.rst184 which prepends a debug header enabling the flash to persist over
/Zephyr-Core-3.5.0/doc/build/dts/
Dintro-syntax-structure.rst311 properties continue to persist for historical reasons in some existing
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-1.13.rst315 * :github:`9667` - LwM2M: Writeable parameter /3311/0/5850 doesn't persist write
Drelease-notes-3.0.rst1187 * :github:`39989` - Zephyr does not persist CCC data written before bonding when bonding has comple…
Drelease-notes-2.5.rst1492 * :github:`29499` - x86 thread stack guards persist after thread exit
Drelease-notes-3.3.rst2136 * A MCUmgr img_mgmt bug whereby the state of an image upload could persist