Lines Matching full:storage

7 configuration and runtime state.  A variety of storage implementations are
10 appropriate storage medium, and even change it later as needs change.  This
27    storage is :ref:`NVS <nvs_api>`.
42     This gets called when the value is loaded from persisted storage with
78     This gets called when loading values from persistent storage using
82     This gets called when saving a single setting to persistent storage using
93 Zephyr Storage Backends
96 Zephyr has three storage backends: a Flash Circular Buffer
98 (:kconfig:option:`CONFIG_SETTINGS_FILE`), or non-volatile storage
112 Non-volatile storage read target is registered using
116 Storage Location
119 The FCB and non-volatile storage (NVS) backends both look for a fixed
120 partition with label "storage" by default. A different partition can be
127 Loading data from persisted storage
131 to load settings data from storage to volatile memory.
142 Storing data to persistent storage
146 settings data to the storage medium. A call to :c:func:`settings_save()` uses an
152 For both FCB and file back-end only storage requests with data which
154 whether a value changed by the application. Such a storage mechanism implies
155 that storage can contain multiple value assignments for a key , while only the
160 When storage becomes full (FCB) or consumes too much space (file),
167 configuration storage simultaneously for the same instance.
176 and ``h_export``. ``h_set`` is called when the value is restored from storage
178 storage thanks to ``storage_func()``. The user can also implement some other
230 persisted storage.