Home
last modified time | relevance | path

Searched refs:h_commit (Results 1 – 11 of 11) sorted by relevance

/Zephyr-latest/tests/subsys/settings_commit_prio/src/
Dmain.c60 .h_commit = commit1,
65 .h_commit = commit3,
/Zephyr-latest/subsys/settings/src/
Dsettings_runtime.c69 if (ch->h_commit) { in settings_runtime_commit()
70 return ch->h_commit(); in settings_runtime_commit()
Dsettings.c278 if (ch->h_commit) { in settings_commit_subtree()
284 rc2 = ch->h_commit(); in settings_commit_subtree()
299 if (ch->h_commit) { in settings_commit_subtree()
305 rc2 = ch->h_commit(); in settings_commit_subtree()
/Zephyr-latest/include/zephyr/settings/
Dsettings.h103 int (*h_commit)(void); member
172 int (*h_commit)(void); member
219 .h_commit = _commit, \
/Zephyr-latest/tests/subsys/settings/fcb/src/
Dsettings_test_fcb.c53 .h_commit = c1_handle_commit,
60 .h_commit = NULL,
67 .h_commit = NULL,
Dsettings_test_compress_deleted.c38 .h_commit = NULL,
/Zephyr-latest/tests/subsys/settings/nvs/src/
Dsettings_test_nvs.c34 .h_commit = c1_handle_commit,
/Zephyr-latest/doc/services/settings/
Dindex.rst46 **h_commit**
58 the ``h_commit`` calls. This can be advantageous when e.g. a subsystem initializes
59 a service that other ``h_commit`` calls depend on.
61 Settings handlers ``h_commit`` routines are by default initialized with ``cprio = 0``,
132 After all data is loaded, the ``h_commit`` handler is issued,
/Zephyr-latest/tests/subsys/settings/functional/src/
Dsettings_basic_test.c194 .h_commit = val1_commit,
211 .h_commit = val2_commit,
228 .h_commit = val3_commit,
/Zephyr-latest/tests/subsys/settings/file/src/
Dsettings_test_file.c34 .h_commit = c1_handle_commit,
/Zephyr-latest/samples/subsys/settings/src/
Dmain.c55 .h_commit = alpha_handle_commit,