Home
last modified time | relevance | path

Searched refs:settings (Results 1 – 25 of 416) sorted by relevance

12345678910>>...17

/Zephyr-Core-3.5.0/subsys/settings/
DKconfig7 The settings subsystem allows its users to serialize and
15 module-str = settings
24 bool "dynamic settings handlers"
27 Enables the use of dynamic settings handlers
29 # Hidden option to enable encoding length into settings entry
40 Storage back-end to be used by the settings subsystem.
46 Use FCB as a settings storage back-end.
53 Use a file (on mounted file system) as a settings storage back-end.
91 Use a custom settings storage back-end.
100 int "Number of flash areas used by the settings subsystem"
[all …]
/Zephyr-Core-3.5.0/samples/subsys/settings/
DREADME.rst1 .. zephyr:code-sample:: settings
3 :relevant-api: settings settings_rt settings_name_proc
5 Load and save configuration values using the settings API.
10 This is a simple application demonstrating use of the settings runtime
13 settings method. The example shows how to implement module handlers, how to
19 * A board with settings support, for instance: nrf52840dk_nrf52840
25 This sample can be found under :zephyr_file:`samples/subsys/settings` in
32 :zephyr-app: samples/subsys/settings
39 settings manipulation messages.
50 settings subsys initialization: OK.
[all …]
/Zephyr-Core-3.5.0/tests/subsys/settings/nvs/src/
DCMakeLists.txt5 ${ZEPHYR_BASE}/subsys/settings/include
6 ${ZEPHYR_BASE}/subsys/settings/src
7 ${ZEPHYR_BASE}/tests/subsys/settings/nvs/src
/Zephyr-Core-3.5.0/tests/subsys/settings/fcb/src/
DCMakeLists.txt7 ${ZEPHYR_BASE}/subsys/settings/include
8 ${ZEPHYR_BASE}/subsys/settings/src
9 ${ZEPHYR_BASE}/tests/subsys/settings/fcb/src
/Zephyr-Core-3.5.0/subsys/mgmt/mcumgr/grp/settings_mgmt/
DCMakeLists.txt8 # interface, when settings management is enabled.
13 message(WARNING "Note: MCUmgr settings management is enabled but settings access hooks are "
15 "use, as all settings on the device can be manipulated by a remote device. See "
DKconfig5 bool "MCUmgr handlers for settings management"
12 Enables MCUmgr handlers for settings manipulation.
57 variable if placed on the heap (settings does not support getting
64 Allows applications to control settings management access by
66 settings read or write attempt is made.
/Zephyr-Core-3.5.0/doc/services/settings/
Dindex.rst6 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
[all …]
/Zephyr-Core-3.5.0/tests/subsys/settings/file/src/
DCMakeLists.txt7 ${ZEPHYR_BASE}/subsys/settings/include
8 ${ZEPHYR_BASE}/subsys/settings/src
9 ${ZEPHYR_BASE}/tests/subsys/settings/file/include
/Zephyr-Core-3.5.0/tests/subsys/settings/functional/src/
DCMakeLists.txt4 ${ZEPHYR_BASE}/subsys/settings/include
5 ${ZEPHYR_BASE}/subsys/settings/src
/Zephyr-Core-3.5.0/doc/services/device_mgmt/smp_groups/
Dsmp_group_3.rst19 | ``2`` | Commit settings |
21 | ``3`` | Load/Save settings |
316 Commit settings command
319 Commit settings command allows committing all settings that have been set but not yet applied on a
322 Commit settings request
325 Commit settings request header fields:
338 Commit settings response
341 Commit settings response header fields:
392 Load/Save settings command
395 Load/Save settings command allows loading/saving all serialized items from/to persistent storage
[all …]
/Zephyr-Core-3.5.0/doc/build/snippets/
Dindex.rst6 Snippets are a way to save build system settings in one place, and then use
7 those settings when you build any Zephyr application. This lets you save common
14 - applying interrelated configuration settings to your "main" CPU and a
Dwriting.rst13 additional build system settings, like this:
18 # ... build system settings go here ...
20 Build system settings go in other keys in the file as described later on in
23 You can combine settings whenever they appear under the same keys. For example,
91 settings:
173 Board-specific settings
176 You can write settings that only apply to some boards.
178 The settings described here are applied in **addition** to snippet settings
191 bar: # settings for board "bar" go here
194 baz: # settings for board "baz" go here
/Zephyr-Core-3.5.0/tests/subsys/settings/functional/file/
DCMakeLists.txt11 ${ZEPHYR_BASE}/subsys/settings/include
12 ${ZEPHYR_BASE}/subsys/settings/src
/Zephyr-Core-3.5.0/subsys/net/lib/http/
Dhttp_parser.c656 const struct http_parser_settings *settings, in zero_content_length() argument
669 rc = cb_notify(parser, &p_state, settings->on_message_complete, in zero_content_length()
688 settings->on_message_complete, in zero_content_length()
708 const struct http_parser_settings *settings, in parser_execute() argument
739 settings->on_message_complete, in parser_execute()
819 settings->on_message_begin, in parser_execute()
871 settings->on_message_begin, in parser_execute()
1000 settings->on_status, in parser_execute()
1042 settings->on_status, in parser_execute()
1068 rc = cb_data(parser, settings->on_status, in parser_execute()
[all …]
Dhttp_client.c379 struct http_parser_settings *settings) in http_client_init_parser() argument
383 settings->on_body = on_body; in http_client_init_parser()
384 settings->on_chunk_complete = on_chunk_complete; in http_client_init_parser()
385 settings->on_chunk_header = on_chunk_header; in http_client_init_parser()
386 settings->on_headers_complete = on_headers_complete; in http_client_init_parser()
387 settings->on_header_field = on_header_field; in http_client_init_parser()
388 settings->on_header_value = on_header_value; in http_client_init_parser()
389 settings->on_message_begin = on_message_begin; in http_client_init_parser()
390 settings->on_message_complete = on_message_complete; in http_client_init_parser()
391 settings->on_status = on_status; in http_client_init_parser()
[all …]
/Zephyr-Core-3.5.0/cmake/modules/
Dbasic_settings.cmake5 # Setup basic settings for a Zephyr project.
7 # Basic settings are:
8 # - sysbuild defined configuration settings
10 # Details for sysbuild settings:
Dconfiguration_files.cmake88 the configuration settings specified in an alternate .conf file using this parameter. \
89 These settings will override the settings in the application’s .config file or its default .conf fi…
113 build the application using the DT configuration settings specified in an \
114 alternate .overlay file using this parameter. These settings will override the \
115 settings in the board's .dts file. Multiple files may be listed, e.g. \
/Zephyr-Core-3.5.0/scripts/ci/
Dupload_test_results_es.py44 settings = {
72 es.indices.create(index=index_name, mappings=mappings, settings=settings)
/Zephyr-Core-3.5.0/cmake/ide/
Declipse_cdt4_generator_amendment.cmake64 ## 3 - work mode: "C and CXX includes, defines in .settings - [EXPERIMENTAL]"
65 ## 4 - work mode: "C and CXX includes, defines in .settings with project defines - [EXPERIMENTAL]"
77 # set(_work_mode "C and CXX includes, defines in .settings - [EXPERIMENTAL]")
81 # set(_work_mode "C and CXX includes, defines in .settings with project defines - [EXPERIMENTAL]")
115 if ( (${_work_mode} STREQUAL "C and CXX includes, defines in .settings - [EXPERIMENTAL]") OR
116 …(${_work_mode} STREQUAL "C and CXX includes, defines in .settings with project defines - [EXPERIME…
118 set(OUTPUT_FILE ${CMAKE_BINARY_DIR}/.settings/language.settings.xml)
127 …if (${_work_mode} STREQUAL "C and CXX includes, defines in .settings with project defines - [EXPER…
128 …_FILE} "\t\t\t<provider class=\"org.eclipse.cdt.managedbuilder.language.settings.providers.GCCBuil…
130 …_FILE} "\t\t\t<provider class=\"org.eclipse.cdt.managedbuilder.language.settings.providers.GCCBuil…
[all …]
/Zephyr-Core-3.5.0/scripts/native_simulator/
D.gitignore11 .settings/*
/Zephyr-Core-3.5.0/tests/subsys/settings/functional/fcb/
Dchosen.overlay7 zephyr,settings-partition = &storage_partition;
/Zephyr-Core-3.5.0/tests/subsys/settings/functional/nvs/
Dchosen.overlay7 zephyr,settings-partition = &storage_partition;
/Zephyr-Core-3.5.0/subsys/retention/
DKconfig.blinfo45 Allows bootloader settings to be fetched by calling a function which
52 Allows bootloader settings to be fetched using settings with the
/Zephyr-Core-3.5.0/samples/bluetooth/iso_broadcast_benchmark/
DREADME.rst51 #. Optionally modify the broadcasting settings.
89 The broadcaster will ask if any changes to the current settings are wanted.
90 If y/Y is chosen, then it will create a prompt to enter changes to the settings,
91 otherwise continue with the current settings. The broadcaster will then start
98 …Change settings (y/N)? (Current settings: rtn=2, interval=7500, latency=10, phy=2, sdu=251, packin…
/Zephyr-Core-3.5.0/samples/net/vlan/
DREADME.rst5 Setup two virtual LAN networks and use net-shell to view the networks' settings.
11 The application sample enables net-shell and allows users to view VLAN settings.
45 with these settings:

12345678910>>...17