/Zephyr-latest/subsys/settings/ |
D | Kconfig | 4 menuconfig SETTINGS config 5 bool "Settings" 7 The settings subsystem allows its users to serialize and 12 if SETTINGS 14 module = SETTINGS 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. [all …]
|
/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/tests/drivers/gpio/gpio_basic_api/boards/ |
D | intel_ehl_crb.overlay | 8 * GPIO Settings -> GPIO_GPP_B -> GPP_B04 -> GPIO Skip -> Disable 9 * GPIO Settings -> GPIO_GPP_B -> GPP_B04 -> PadMode -> GPIO control of the pad 10 * GPIO Settings -> GPIO_GPP_B -> GPP_B04 -> HostSoftPadOwn -> Host ownership to GPIO Driver mode 11 * GPIO Settings -> GPIO_GPP_B -> GPP_B04 -> Direction -> DirOut 12 * GPIO Settings -> GPIO_GPP_B -> GPP_B04 -> LockConfig -> PadUnlock 13 * GPIO Settings -> GPIO_GPP_B -> GPP_B23 -> GPIO Skip -> Disable 14 * GPIO Settings -> GPIO_GPP_B -> GPP_B23 -> PadMode -> GPIO control of the pad 15 * GPIO Settings -> GPIO_GPP_B -> GPP_B23 -> HostSoftPadOwn -> Host ownership to GPIO Driver mode 16 * GPIO Settings -> GPIO_GPP_B -> GPP_B23 -> Direction -> DirIn 17 * GPIO Settings -> GPIO_GPP_B -> GPP_B23 -> LockConfig -> PadUnlock
|
/Zephyr-latest/tests/subsys/settings/functional/nvs/ |
D | testcase.yaml | 2 settings.functional.nvs: 8 - settings 10 settings.functional.nvs.chosen: 16 - settings 18 settings.functional.nvs.dk: 26 - settings
|
/Zephyr-latest/samples/subsys/settings/ |
D | README.rst | 1 .. zephyr:code-sample:: settings 2 :name: Settings API 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. [all …]
|
D | sample.yaml | 2 name: Settings Sample 5 sample.subsys.settings: 6 tags: settings 43 - "The settings destination off the key <alpha/beta/source> has got value:\ 45 - "String value \"rtos\" was retrieved from the settings destination off the\
|
/Zephyr-latest/drivers/input/ |
D | Kconfig.analog_axis | 28 bool "Analog axis settings support" 30 depends on SETTINGS 32 Settings support for the analog axis driver, exposes a 34 settings and load them automatically on startup. 37 int "Maximum number of axes supported in the settings." 41 settings.
|
/Zephyr-latest/subsys/net/lib/wifi_credentials/ |
D | wifi_credentials_backend_settings.c | 10 #include <zephyr/settings/settings.h> 44 LOG_ERR("Settings error: invalid settings length"); in zephyr_settings_backend_load_val_cb() 52 LOG_ERR("Settings error: entry incomplete"); in zephyr_settings_backend_load_val_cb() 69 LOG_ERR("Settings error: no key"); in zephyr_settings_backend_load_key_cb() 76 LOG_ERR("Settings error: index too large"); in zephyr_settings_backend_load_key_cb() 81 LOG_ERR("Settings error: invalid settings length"); in zephyr_settings_backend_load_key_cb() 90 LOG_ERR("Settings error: entry incomplete"); in zephyr_settings_backend_load_key_cb() 103 LOG_ERR("Initializing settings subsystem failed: %d", ret); in wifi_credentials_backend_init() 121 LOG_ERR("WiFi credentials settings key could not be generated, idx: %d", idx); in wifi_credentials_store_entry() 136 LOG_ERR("WiFi credentials settings key could not be generated, idx: %d", idx); in wifi_credentials_delete_entry() [all …]
|
D | wifi_credentials_internal.h | 15 * @param buf encoded settings entry 28 * @brief Stores settings entry in flash. 31 * @param buf encoded settings entry 38 * @brief Deletes settings entry from flash. 46 * @brief Loads settings entry from flash. 49 * @param buf encoded settings entry
|
/Zephyr-latest/doc/services/settings/ |
D | index.rst | 3 Settings chapter 6 The settings subsystem gives modules a way to store persistent per-device 14 Settings items are stored as key-value pair strings. By convention, 22 For an example of the settings subsystem refer to :zephyr:code-sample:`settings` sample. 32 Settings handlers for subtree implement a set of handler functions. 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 [all …]
|
/Zephyr-latest/subsys/mgmt/mcumgr/grp/settings_mgmt/ |
D | CMakeLists.txt | 7 # Settings management group public API is exposed by MCUmgr API 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" 6 depends on SETTINGS 12 Enables MCUmgr handlers for settings manipulation. 57 variable if placed on the heap (settings does not support getting 61 bool "Settings access hook" 64 Allows applications to control settings management access by 66 settings read or write attempt is made.
|
/Zephyr-latest/tests/subsys/settings/functional/fcb/ |
D | testcase.yaml | 2 settings.functional.fcb: 12 - settings 14 settings.functional.fcb.chosen: 23 - settings
|
/Zephyr-latest/subsys/settings/include/settings/ |
D | settings_file.h | 12 #include <zephyr/settings/settings.h> 18 #define SETTINGS_FILE_NAME_MAX 32 /* max length for settings filename */ 27 /* register file to be source of settings */ 30 /* settings saves go to a file */
|
/Zephyr-latest/include/zephyr/settings/ |
D | settings.h | 30 * @defgroup settings Settings 37 #define SETTINGS_MAX_DIR_DEPTH 8 /* max depth of settings tree */ 43 /* place for settings additions: 49 * Function used to read the data from the settings storage in 77 /**< Get values handler of settings items identified by keyword names. 90 /**< Set value handler of settings items identified by keyword names. 104 /**< This handler gets called after settings has been loaded in full. 112 /**< This gets called to dump all current settings items. 114 * This happens when @ref settings_save tries to save the settings. 117 * a single key-value pair to persisted settings. Don't store [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/subsys/retention/ |
D | Kconfig.blinfo | 45 Allows bootloader settings to be fetched by calling a function which 49 bool "Settings" 50 depends on SETTINGS 52 Allows bootloader settings to be fetched using settings with the
|
/Zephyr-latest/tests/bsim/bluetooth/host/id/settings/src/ |
D | dut.c | 9 #include <zephyr/settings/settings.h> 34 FAIL("Failed to load settings (err %d)\n", err); in run_dut1() 38 LOG_DBG("Number of Bluetooth identities after settings load: %d", bt_id_count); in run_dut1() 71 FAIL("Failed to load settings (err %d)\n", err); in run_dut2() 74 LOG_DBG("Settings loaded"); in run_dut2()
|
/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/samples/net/lldp/ |
D | prj.conf | 38 # First ethernet interface will use these settings 44 # Second ethernet interface will have these settings 51 # Settings for the third network interface 61 # VLAN settings. We will have two VLANs in this sample. 65 # LLDP settings
|
/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/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" 36 select SETTINGS 66 string "Subtree in which to store the settings, with a trailing slash. Can be empty."
|
/Zephyr-latest/subsys/lorawan/nvm/ |
D | Kconfig | 8 default LORAWAN_NVM_SETTINGS if SETTINGS 20 bool "Settings based NVM" 21 depends on SETTINGS
|
/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/samples/net/vlan/ |
D | prj.conf | 38 # First ethernet interface will use these settings 44 # Second VLAN supported network interface will have these settings 52 # Settings for the third VLAN supported network interface 63 # VLAN settings.
|