Lines Matching refs:settings

6 The settings subsystem gives modules a way to store persistent per-device
22 For an example of the settings subsystem refer to :zephyr:code-sample:`settings` sample.
36     This gets called when asking for a settings element value by its name using
45     This gets called after the settings have been loaded in full.
47     effect right away, for example if there are multiple settings
51     This gets called to write all current settings. This happens
52     when ``settings_save()`` tries to save the settings or transfer to any
74     This gets called when starting a save of all current settings using
78     This gets called after having saved of all current settings using
89 You can declare multiple sources for settings; settings from
92 There can be only one target for writing settings; this is where
109 selected by setting the ``zephyr,settings-partition`` property of the
112 The file path used by the file backend to store settings is selected via the
119 to load settings data from storage to volatile memory.
121 signalling the application that the settings were successfully
134 settings data to the storage medium. A call to ``settings_save()`` uses an
152 Secure domain settings
154 Currently settings doesn't provide scheme of being secure, and non-secure
156 It is recommended that secure domain uses its own settings instance and it might
163 This is a simple example, where the settings handler only implements ``h_set``
229     #include <zephyr/settings/settings.h>
322 The Settings subsystem APIs are provided by ``settings.h``:
324 API for general settings usage
326 .. doxygengroup:: settings
332 API for runtime settings manipulation