Searched full:configuration (Results 1 – 25 of 3574) sorted by relevance
12345678910>>...143
| /Zephyr-Core-3.5.0/subsys/usb/device_next/ |
| D | usbd_config.h | 13 * @brief Get configuration descriptor bConfigurationValue value
15 * @param[in] cfg_nd Pointer to a configuration node structure
27 * @brief Set configuration descriptor bConfigurationValue value
29 * @param[in] cfg_nd Pointer to a configuration node structure
40 * @brief Get configuration node
42 * Get configuration node with desired configuration number.
45 * @param[in] cfg Configuration number (bConfigurationValue)
47 * @return pointer to configuration node or NULL if does not exist
53 * @brief Get selected configuration node
55 * Get configuration node based on configuration selected by the host.
[all …]
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
| D | sar_cfg_cli.rst | 3 SAR Configuration Client
6 The SAR Configuration Client model is a foundation model defined by the Bluetooth mesh
8 :kconfig:option:`CONFIG_BT_MESH_SAR_CFG_CLI` configuration option.
10 The SAR Configuration Client model is introduced in the Bluetooth Mesh Protocol Specification
11 version 1.1, and it supports the configuration of the lower transport layer behavior of a node that
14 The model can send messages to query or change the states supported by the SAR Configuration Server
15 (SAR Transmitter and SAR Receiver) using SAR Configuration messages.
18 Configuration Server. Function calls :c:func:`bt_mesh_sar_cfg_cli_transmitter_get` and
23 Configuration Server. Function calls :c:func:`bt_mesh_sar_cfg_cli_receiver_get` and
29 An element can send any SAR Configuration Client message at any time to query or change the states
[all …]
|
| D | cfg.rst | 3 Runtime Configuration
6 The runtime configuration API allows applications to change their runtime
7 configuration directly, without going through the Configuration models.
12 Configuration Client can communicate with to change the node configuration. In some
13 cases, the mesh node can't rely on the Configuration Client to detect or determine
15 scenarios, this API can be used to change the configuration locally.
18 Runtime configuration changes before the node is provisioned will not be stored
|
| D | cfg_cli.rst | 3 Configuration Client
6 The Configuration Client model is a foundation model defined by the Bluetooth mesh
8 mesh node, including encryption keys, model configuration and feature
11 The Configuration Client model communicates with a
13 node. The Configuration Client model may communicate with servers on other
14 nodes or self-configure through the local Configuration Server model.
16 All configuration functions in the Configuration Client API have ``net_idx``
20 The Configuration Client model is optional, and it must only be instantiated on the
|
| D | sar_cfg_srv.rst | 3 SAR Configuration Server
6 The SAR Configuration Server model is a foundation model defined by the Bluetooth mesh
8 :kconfig:option:`CONFIG_BT_MESH_SAR_CFG_SRV` configuration option.
10 The SAR Configuration Server model is introduced in the Bluetooth Mesh Protocol Specification
11 version 1.1, and it supports the configuration of the
13 The model defines a set of states and messages for the SAR configuration.
15 The SAR Configuration Server model defines two states, SAR Transmitter state and SAR Receiver state.
20 The SAR Configuration Server model does not have an API of its own, but relies on a
21 :ref:`bluetooth_mesh_sar_cfg_cli` to control it. The SAR Configuration Server model only accepts
24 If present, the SAR Configuration Server model must only be instantiated on the primary element.
|
| D | srpl_cli.rst | 3 Solicitation PDU RPL Configuration Client
6 The Solicitation PDU RPL Configuration Client model is a foundation model defined by the Bluetooth
10 The Solicitation PDU RPL Configuration Client model was introduced in the Bluetooth Mesh Protocol
15 The Solicitation PDU RPL Configuration Client model communicates with a Solicitation PDU RPL
16 Configuration Server model using the application keys configured by the Configuration Client.
18 If present, the Solicitation PDU RPL Configuration Client model must only be instantiated on the
24 The Solicitation PDU RPL Configuration Client model behavior can be configured with the transmission
27 Configuration Client waits for a response message to arrive in milliseconds. This value can be
|
| D | srpl_srv.rst | 3 Solicitation PDU RPL Configuration Server
6 The Solicitation PDU RPL Configuration Server model is a foundation model defined by the Bluetooth
9 The Solicitation PDU RPL Configuration Server model was introduced in the Bluetooth Mesh Protocol
15 The Solicitation PDU RPL Configuration Server does not have an API of its own, and relies on a
17 application key as configured by the Configuration Client.
19 If present, the Solicitation PDU RPL Configuration Server model must only be instantiated on the
25 For the Solicitation PDU RPL Configuration Server model, the
|
| /Zephyr-Core-3.5.0/dts/bindings/ethernet/ |
| D | silabs,gecko-ethernet.yaml | 30 description: location of RMII pins, configuration defined as <location>
36 description: location of MDC and MDIO pins, configuration defined as <location>
42 description: PHY MDC individual pin configuration defined as <location port pin>
47 description: PHY MDIO individual pin configuration defined as <location port pin>
53 description: Reference clock individual pin configuration defined as <location port pin>
58 description: Receive data valid individual pin configuration defined as <location port pin>
63 description: Transmit data 0 individual pin configuration defined as <location port pin>
68 description: Transmit data 1 individual pin configuration defined as <location port pin>
73 description: Transmit enable individual pin configuration defined as <location port pin>
78 description: Receive data 0 individual pin configuration defined as <location port pin>
[all …]
|
| /Zephyr-Core-3.5.0/doc/build/kconfig/ |
| D | setting.rst | 3 Setting Kconfig configuration values
26 up in the interactive configuration interfaces (hence *visible*), and can be
27 set in configuration files.
44 not shown in the interactive configuration interfaces, and users have no
61 Setting symbols in configuration files
64 Visible symbols can be configured by setting them in configuration files. The
65 initial configuration is produced by merging a :file:`*_defconfig` file for the
69 Assignments in configuration files use this syntax:
94 This is the format you will see in the merged configuration in
97 This style is accepted for historical reasons: Kconfig configuration files
[all …]
|
| D | index.rst | 3 Configuration System (Kconfig)
7 for specific application and platform needs. Configuration is handled through
8 Kconfig, which is the same configuration system used by the Linux kernel. The
9 goal is to support configuration without having to change any source code.
11 Configuration options (often called *symbols*) are defined in :file:`Kconfig`
14 keep the interactive configuration interfaces organized.
20 The following sections explain how to set Kconfig configuration options, go
33 Users interested in optimizing their configuration for security should refer
|
| D | menuconfig.rst | 6 There are two interactive configuration interfaces available for exploring the
9 terminal, while ``guiconfig`` is a graphical configuration interface.
13 The configuration can also be changed by editing :file:`zephyr/.config` in
14 the application build directory by hand. Using one of the configuration
16 configuration symbols.
27 Saving a minimal configuration file (with e.g. :kbd:`D` in menuconfig) and
29 configuration file only lists symbols that differ from their default value.
31 To run one of the configuration interfaces, do this:
94 #. Change configuration values in the ``menuconfig`` interface as follows:
103 Boolean configuration options are shown with :guilabel:`[ ]` brackets,
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm64/fvp_baser_aemv8r/doc/ |
| D | debug-with-arm-ds.rst | 37 Create a new configuration database
40 Create a new configuration database by selecting ``File -> New -> Other... -> Configuration Databas…
42 .. image:: images/create-new-configuration-database.jpg
44 :alt: Arm DS create new configuration database
48 .. image:: images/create-new-configuration-database_database-name.jpg
50 :alt: Arm DS create new configuration database: choose database name
52 Click ``Finish`` and the new configuration database can be seen in ``Project Explorer``:
54 .. image:: images/create-new-configuration-database_shown-in-project-explorer.jpg
56 :alt: Arm DS create new configuration database: shown in project explorer
58 Create a new model configuration
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1050_evk/ |
| D | CMakeLists.txt | 22 "update your flash configuration or device configuration data blocks")
23 # Default EVK configuration uses hyperflash, so use that file
29 # Include flash configuration block for RT1050 EVK from NXP's HAL.
30 # This configuration block may need modification if another flash chip is
38 # Include device configuration data block for RT1050 EVK from NXP's HAL.
39 # This configuration block may need modification if another SDRAM chip
46 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1020_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
18 # Include flash configuration block for RT1020 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
27 # Include device configuration data block for RT1020 EVK from NXP's HAL.
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1024_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
18 # Include flash configuration block for RT1024 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
27 # Include device configuration data block for RT1024 EVK from NXP's HAL.
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1040_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
18 # Include flash configuration block for RT1040 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
27 # Include device configuration data block for RT1040 EVK from NXP's HAL.
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1060_evk/ |
| D | CMakeLists.txt | 19 # No flash configuration block exists for the RT1060 with HyperFlash in
30 "update your flash configuration or device configuration data blocks")
31 # Default EVK configuration uses qspi, so use that file
38 # Include flash configuration block for RT1060 EVK from NXP's HAL.
39 # This configuration block may need modification if another flash chip is
47 # Include device configuration data block for RT1060 EVK from NXP's HAL.
48 # This configuration block may need modification if another SDRAM chip
55 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1064_evk/ |
| D | CMakeLists.txt | 18 "update your flash configuration or device configuration data blocks")
23 # Include flash configuration block for RT1064 EVK from NXP's HAL.
24 # This configuration block may need modification if another flash chip is
32 # Include device configuration data block for RT1064 EVK from NXP's HAL.
33 # This configuration block may need modification if another SDRAM chip
40 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1160_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
18 # Include flash configuration block for RT1160 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
27 # Include device configuration data block for RT1160 EVK from NXP's HAL.
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/controller/ll_sw/nordic/lll/ |
| D | lll_df_internal.h | 11 /* Enables CTE transmission according to provided configuration */
15 /* Allocate memory for new DF sync configuration. It will always return the same
20 /* Returns pointer to last allocated DF sync configuration. If it is called before
29 /* Enqueue new DF sync configuration data. */
35 /* Get latest DF sync configuration data. Latest configuration data are the one
40 /* Get current DF sync configuration data. Current configuration data
49 /* Return information if DF sync configuration data were modified since last
57 /* Enables CTE reception according to provided configuration */
|
| /Zephyr-Core-3.5.0/include/zephyr/bluetooth/audio/ |
| D | bap_lc3_preset.h | 31 * @brief Helper to declare LC3 Unicast 8_1_1 codec configuration
41 * @brief Helper to declare LC3 Unicast 8_2_1 codec configuration
51 * @brief Helper to declare LC3 Unicast 16_1_1 codec configuration
61 * @brief Helper to declare LC3 Unicast 16_2_1 codec configuration
73 * @brief Helper to declare LC3 Unicast 24_1_1 codec configuration
83 * @brief Helper to declare LC3 Unicast 24_2_1 codec configuration
95 * @brief Helper to declare LC3 Unicast 32_1_1 codec configuration
105 * @brief Helper to declare LC3 Unicast 32_2_1 codec configuration
115 * @brief Helper to declare LC3 Unicast 441_1_1 codec configuration
126 * @brief Helper to declare LC3 Unicast 441_2_1 codec configuration
[all …]
|
| D | lc3.h | 166 * @brief Codec configuration type IDs
175 /** @brief LC3 Sample Frequency configuration type. */
178 /** @brief LC3 Frame Duration configuration type. */
181 /** @brief LC3 channel Allocation configuration type. */
184 /** @brief LC3 Frame Length configuration type. */
187 /** @brief Codec frame blocks, per SDU configuration type. */
193 * @brief 8 Khz codec Sample Frequency configuration
197 * @brief 11.025 Khz codec Sample Frequency configuration
201 * @brief 16 Khz codec Sample Frequency configuration
205 * @brief 22.05 Khz codec Sample Frequency configuration
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1170_evk/ |
| D | CMakeLists.txt | 15 "update your flash configuration or device configuration data blocks")
27 # Include flash configuration block for RT1170 EVK from NXP's HAL.
28 # This configuration block may need modification if another flash chip is
36 # Include device configuration data block for RT1170 EVK from NXP's HAL.
37 # This configuration block may need modification if another SDRAM chip
44 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/soc/arm/silabs_exx32/common/ |
| D | pinctrl_soc.h | 57 * @param pincfg Pin configuration bit field.
62 * @brief Utility macro to obtain port configuration.
64 * @param pincfg port configuration bit field.
69 * @brief Utility macro to obtain pin configuration.
71 * @param pincfg pin configuration bit field.
76 * @brief Utility macro to obtain location configuration.
78 * @param pincfg Loc configuration bit field.
83 * @brief Utility macro to obtain speed configuration.
85 * @param pincfg speed configuration bit field.
|
| /Zephyr-Core-3.5.0/dts/bindings/pinctrl/ |
| D | pinctrl-device.yaml | 10 more information on what is the expected pin configuration format.
16 Pin configuration/s for the first state. Content is specific to the
22 Pin configuration/s for the second state. See pinctrl-0.
27 Pin configuration/s for the third state. See pinctrl-0.
32 Pin configuration/s for the fourth state. See pinctrl-0.
37 Pin configuration/s for the fifth state. See pinctrl-0.
|
12345678910>>...143
