| /Zephyr-latest/drivers/pinctrl/ |
| D | pinctrl_imx_scmi.c | 12 struct scmi_pinctrl_settings settings; in scmi_pinctrl_configure_pin() local
18 settings.id = (pin->pinmux.mux_register - IOMUXC_MUXREG) / 4; in scmi_pinctrl_configure_pin()
19 settings.config[0] = PIN_CONFIG_TYPE_MUX; in scmi_pinctrl_configure_pin()
20 settings.config[1] = IOMUXC_INPUT_ENABLE(pin->pin_ctrl_flags) in scmi_pinctrl_configure_pin()
26 settings.config[2] = PIN_CONFIG_TYPE_DAISY_ID; in scmi_pinctrl_configure_pin()
27 settings.config[3] = (pin->pinmux.input_register - IOMUXC_DAISYREG) / 4; in scmi_pinctrl_configure_pin()
30 settings.config[4] = PIN_CONFIG_TYPE_DAISY_CFG; in scmi_pinctrl_configure_pin()
31 settings.config[5] = pin->pinmux.input_daisy; in scmi_pinctrl_configure_pin()
35 settings.attributes = in scmi_pinctrl_configure_pin()
38 ret = scmi_pinctrl_settings_configure(&settings); in scmi_pinctrl_configure_pin()
[all …]
|
| /Zephyr-latest/subsys/settings/ |
| D | Kconfig | 7 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.
83 Use a custom settings storage back-end.
92 int "Number of flash areas used by the settings subsystem"
[all …]
|
| /Zephyr-latest/samples/subsys/settings/ |
| D | README.rst | 1 .. 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-latest/drivers/firmware/scmi/ |
| D | pinctrl.c | 11 int scmi_pinctrl_settings_configure(struct scmi_pinctrl_settings *settings) in scmi_pinctrl_settings_configure() argument
21 if (!settings) { in scmi_pinctrl_settings_configure()
33 config_num = SCMI_PINCTRL_ATTRIBUTES_CONFIG_NUM(settings->attributes); in scmi_pinctrl_settings_configure()
45 msg.len = sizeof(*settings) - in scmi_pinctrl_settings_configure()
47 msg.content = settings; in scmi_pinctrl_settings_configure()
|
| /Zephyr-latest/tests/subsys/settings/nvs/src/ |
| D | CMakeLists.txt | 5 ${ZEPHYR_BASE}/subsys/settings/include
6 ${ZEPHYR_BASE}/subsys/settings/src
7 ${ZEPHYR_BASE}/tests/subsys/settings/nvs/src
|
| /Zephyr-latest/tests/subsys/settings/fcb/src/ |
| D | CMakeLists.txt | 7 ${ZEPHYR_BASE}/subsys/settings/include
8 ${ZEPHYR_BASE}/subsys/settings/src
9 ${ZEPHYR_BASE}/tests/subsys/settings/fcb/src
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/settings_mgmt/ |
| D | CMakeLists.txt | 8 # 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 "
|
| D | Kconfig | 5 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-latest/tests/subsys/settings/file/src/ |
| D | CMakeLists.txt | 7 ${ZEPHYR_BASE}/subsys/settings/include
8 ${ZEPHYR_BASE}/subsys/settings/src
9 ${ZEPHYR_BASE}/tests/subsys/settings/file/include
|
| /Zephyr-latest/doc/services/settings/ |
| D | index.rst | 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.
38 This gets called when asking for a settings element value by its name using
47 This gets called after the settings have been loaded in full.
49 effect right away, for example if there are multiple settings
53 This gets called to write all current settings. This happens
54 when :c:func:`settings_save()` tries to save the settings or transfer to any
62 initializing a settings handler with a different priority is done using a call to
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
[all …]
|
| /Zephyr-latest/tests/subsys/settings/functional/src/ |
| D | CMakeLists.txt | 4 ${ZEPHYR_BASE}/subsys/settings/include
5 ${ZEPHYR_BASE}/subsys/settings/src
|
| /Zephyr-latest/drivers/input/ |
| D | Kconfig.analog_axis | 28 bool "Analog axis settings support"
34 settings and load them automatically on startup.
37 int "Maximum number of axes supported in the settings."
41 settings.
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_3.rst | 19 | ``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-latest/doc/build/snippets/ |
| D | index.rst | 6 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
|
| D | writing.rst | 13 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,
100 settings:
196 Board-specific settings
199 You can write settings that only apply to some boards.
201 The settings described here are applied in **addition** to snippet settings
214 bar: # settings for board "bar" go here
217 baz: # settings for board "baz" go here
|
| /Zephyr-latest/tests/subsys/settings/functional/file/ |
| D | CMakeLists.txt | 11 ${ZEPHYR_BASE}/subsys/settings/include
12 ${ZEPHYR_BASE}/subsys/settings/src
|
| /Zephyr-latest/cmake/modules/ |
| D | basic_settings.cmake | 5 # Setup basic settings for a Zephyr project.
7 # Basic settings are:
8 # - sysbuild defined configuration settings
10 # Details for sysbuild settings:
|
| D | soc_v2.cmake | 5 # Configure SoC settings based on Kconfig settings.
8 # on Kconfig settings for the selected SoC.
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | http_parser.c | 656 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 …]
|
| /Zephyr-latest/samples/boards/st/bluetooth/interactive_gui/ |
| D | README.rst | 21 Default UART settings
24 It depends on the board default settings for ``zephyr,bt-c2h-uart`` DTS property.
25 The UART default settings are:
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | Kconfig.its_store | 8 DT_CHOSEN_Z_SETTINGS_PARTITION := zephyr,settings-partition
22 overhead compared to the settings-based implementation, both in terms of runtime
23 execution and storage space, and also ROM footprint if the settings subsystem is disabled.
28 bool "ITS store module implementation using the settings subsystem for storage"
66 string "Subtree in which to store the settings, with a trailing slash. Can be empty."
|
| /Zephyr-latest/cmake/ide/ |
| D | eclipse_cdt4_generator_amendment.cmake | 64 ## 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-latest/scripts/native_simulator/ |
| D | .gitignore | 11 .settings/*
|
| /Zephyr-latest/tests/subsys/settings/functional/fcb/ |
| D | chosen.overlay | 7 zephyr,settings-partition = &storage_partition;
|
| /Zephyr-latest/tests/subsys/settings/functional/nvs/ |
| D | chosen.overlay | 7 zephyr,settings-partition = &storage_partition;
|
