Lines Matching full:using

8 provided behind a common API using FCB, NVS, ZMS or a file system.  These
33 These are registered using a call to :c:func:`settings_register()` for
34 dynamic handlers or defined using a call to :c:macro:`SETTINGS_STATIC_HANDLER_DEFINE()`
38     This gets called when asking for a settings element value by its name using
43     :c:func:`settings_load()`, or when using :c:func:`settings_runtime_set()` from the
62 initializing a settings handler with a different priority is done using a call to
63 :c:func:`settings_register_with_cprio()` for dynamic handlers or using a call to
71 implement a set of handler functions. These are registered using a call to
78     This gets called when loading values from persistent storage using
82     This gets called when saving a single setting to persistent storage using
86     This gets called when starting a save of all current settings using
90     This gets called after having saved of all current settings using
109 FCB read target is registered using :c:func:`settings_fcb_src()`, and write target
110 using :c:func:`settings_fcb_dst()`. As a side-effect,  :c:func:`settings_fcb_src()`
112 :c:func:`settings_fcb_dst()`. File read target is registered using
113 :c:func:`settings_file_src()`, and write target by using :c:func:`settings_file_dst()`.
115 Non-volatile storage read target is registered using
116 :c:func:`settings_nvs_src()`, and write target by using
119 Zephyr Memory Storage (ZMS) read target is registered using :c:func:`settings_zms_src()`,
120 and write target is registered using :c:func:`settings_zms_dst()`.
122 ZMS backend has the particularity of using hash functions to hash the settings
162 ``h_export`` implementation to store different data in one operation using
184 provide data for non-secure domain using dedicated interface if needed