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>`.
40     This gets called when the value is loaded from persisted storage with
66     This gets called when loading values from persistent storage using
70     This gets called when saving a single setting to persistent storage using
81 Zephyr Storage Backends
84 Zephyr has three storage backends: a Flash Circular Buffer
86 (:kconfig:option:`CONFIG_SETTINGS_FILE`), or non-volatile storage
100 Non-volatile storage read target is registered using
104 Storage Location
107 The FCB and non-volatile storage (NVS) backends both look for a fixed
108 partition with label "storage" by default. A different partition can be
115 Loading data from persisted storage
119 to load settings data from storage to volatile memory.
130 Storing data to persistent storage
134 settings data to the storage medium. A call to ``settings_save()`` uses an
140 For both FCB and file back-end only storage requests with data which
142 whether a value changed by the application. Such a storage mechanism implies
143 that storage can contain multiple value assignments for a key , while only the
148 When storage becomes full (FCB) or consumes too much space (file),
155 configuration storage simultaneously for the same instance.
164 and ``h_export``. ``h_set`` is called when the value is restored from storage
166 storage thanks to ``storage_func()``. The user can also implement some other
218 persisted storage.