| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight-config.rst | 4 CoreSight System Configuration Manager
13 The CoreSight System Configuration manager is an API that allows the
26 This section introduces the basic concepts of a CoreSight system configuration.
38 CoreSight device is registered with the configuration manager.
49 A feature is enabled as part of a configuration being enabled on the system.
76 A configuration defines a set of features that are to be used in a trace
77 session where the configuration is selected. For any trace session only one
78 configuration may be selected.
81 to support system configuration. A configuration may select features to be
85 As with the feature, a descriptor is used to define the configuration.
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | fsl_immap.h | 23 u32 cs0_config; /* Chip Select Configuration */
24 u32 cs1_config; /* Chip Select Configuration */
25 u32 cs2_config; /* Chip Select Configuration */
26 u32 cs3_config; /* Chip Select Configuration */
28 u32 cs0_config_2; /* Chip Select Configuration 2 */
29 u32 cs1_config_2; /* Chip Select Configuration 2 */
30 u32 cs2_config_2; /* Chip Select Configuration 2 */
31 u32 cs3_config_2; /* Chip Select Configuration 2 */
33 u32 timing_cfg_3; /* SDRAM Timing Configuration 3 */
34 u32 timing_cfg_0; /* SDRAM Timing Configuration 0 */
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | configuration_tests.cpp | 18 #include "configuration.hpp"
66 Configuration configuration(volts, std::move(actions)); in TEST() local
67 EXPECT_EQ(configuration.getVolts().has_value(), true); in TEST()
68 EXPECT_EQ(configuration.getVolts().value(), 1.3); in TEST()
69 EXPECT_EQ(configuration.getActions().size(), 2); in TEST()
79 Configuration configuration(volts, std::move(actions)); in TEST() local
80 EXPECT_EQ(configuration.getVolts().has_value(), false); in TEST()
81 EXPECT_EQ(configuration.getActions().size(), 1); in TEST()
108 // Create Configuration with no volts value specified in TEST()
112 std::unique_ptr<Configuration> configuration = in TEST() local
[all …]
|
| /openbmc/u-boot/arch/x86/include/asm/ |
| H A D | mpspec.h | 22 u32 mpf_physptr; /* Configuration table address */
26 u8 mpf_feature1; /* Predefined or Unique configuration? */
51 /* Base MP configuration table entry types */
147 /* Extended MP configuration table entry types */
217 * mp_next_mpc_entry() - Compute MP configuration table end to be used as
220 * This computes the end address of current MP configuration table, without
221 * counting any extended configuration table entry.
223 * @mc: configuration table header address
224 * @return: configuration table end address
232 * mp_add_mpc_entry() - Add a base MP configuration table entry
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | custom-distribution.rst | 20 configuration file, and then adding any needed code and Metadata to the
26 layer for configuration and code. Using your own layer as compared to
27 just placing configurations in a ``local.conf`` configuration file
28 makes it easier to reproduce the same build configuration when using
33 - *Create the distribution configuration file:* The distribution
34 configuration file needs to be created in the ``conf/distro``
43 You can split out parts of your configuration file into include files
44 and then "require" them from within your distribution configuration
50 Your configuration file needs to set the following required
58 from the distribution configuration file:
[all …]
|
| /openbmc/entity-manager/schemas/ |
| H A D | README.md | 1 # Entity manager configuration file schema
3 Entity manager configuration files are JSON documents and can be validated with
5 of an entity manager configuration file.
7 An entity manager configuration file consists of one or more entity manager
9 configuration data for an entire platform or set of platforms can be expressed
14 entity manager configuration file and schema file names must be
17 ## A single entity manager configuration
20 event occurs. As such, an entity manager configuration provides a syntax for
27 The type property identifies the type of the configuration. When exported,
28 configuration data will be instantiated as grandchildren of
[all …]
|
| /openbmc/u-boot/arch/arm/include/asm/arch-sunxi/ |
| H A D | clock_sun9i.h | 12 u32 pll1_c0_cfg; /* 0x00 c0cpu# pll configuration */
13 u32 pll2_c1_cfg; /* 0x04 c1cpu# pll configuration */
14 u32 pll3_audio_cfg; /* 0x08 audio pll configuration */
15 u32 pll4_periph0_cfg; /* 0x0c peripheral0 pll configuration */
16 u32 pll5_ve_cfg; /* 0x10 videoengine pll configuration */
17 u32 pll6_ddr_cfg; /* 0x14 ddr pll configuration */
18 u32 pll7_video0_cfg; /* 0x18 video0 pll configuration */
19 u32 pll8_video1_cfg; /* 0x1c video1 pll configuration */
20 u32 pll9_gpu_cfg; /* 0x20 gpu pll configuration */
21 u32 pll10_de_cfg; /* 0x24 displayengine pll configuration */
[all …]
|
| /openbmc/phosphor-fan-presence/control/json/ |
| H A D | config_base.hpp | 33 * Configuration object key to uniquely map to the configuration object
35 * std::string = Configuration object's name
36 * std::vector<std::string> = List of profiles the configuration object
42 * @class ConfigBase - Base configuration object
44 * Base class for fan control's JSON configuration objects.
58 // Set the name of this configuration object in ConfigBase()
83 * @brief Get the configuration object's name
85 * @return Name of the configuration object
93 * @brief Get the configuration object's list of profiles
95 * Gets the list of profiles this configuration object belongs to if any
[all …]
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | dcbnl.h | 36 * @willing: willing bit in ETS configuration TLV
281 * @DCB_CMD_PGTX_GCFG: request the priority group configuration for Tx
282 * @DCB_CMD_PGTX_SCFG: set the priority group configuration for Tx
283 * @DCB_CMD_PGRX_GCFG: request the priority group configuration for Rx
284 * @DCB_CMD_PGRX_SCFG: set the priority group configuration for Rx
285 * @DCB_CMD_PFC_GCFG: request the priority flow control configuration
286 * @DCB_CMD_PFC_SCFG: set the priority flow control configuration
293 * @DCB_CMD_GBCN: set backward congestion notification configuration
294 * @DCB_CMD_SBCN: get backward congestion notification configuration.
295 * @DCB_CMD_GAPP: get application protocol configuration
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | configuration.hpp | 37 * @class Configuration
39 * Configuration changes that should be applied to a device or regulator rail.
42 * The most common configuration change is setting the output voltage for a
46 * The configuration changes are applied during the boot before regulators are
49 * The configuration changes are applied by executing one or more actions.
56 class Configuration class
60 Configuration() = delete;
61 Configuration(const Configuration&) = delete;
62 Configuration(Configuration&&) = delete;
63 Configuration& operator=(const Configuration&) = delete;
[all …]
|
| H A D | rail.hpp | 18 #include "configuration.hpp"
57 * @param configuration configuration changes to apply to this rail, if any
62 std::unique_ptr<Configuration> configuration = nullptr, in Rail() argument
64 id{id}, configuration{std::move(configuration)}, in Rail()
81 * Applies the configuration changes that are defined for this rail, if any.
95 * Returns the configuration changes to apply to this rail, if any.
97 * @return Pointer to Configuration object. Will equal nullptr if no
98 * configuration changes are defined for this rail.
100 const std::unique_ptr<Configuration>& getConfiguration() const in getConfiguration()
102 return configuration; in getConfiguration()
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | rio_drv.h | 46 * rio_local_read_config_32 - Read 32 bits from local configuration space
48 * @offset: Offset into local configuration space
52 * device's configuration space.
61 * rio_local_write_config_32 - Write 32 bits to local configuration space
63 * @offset: Offset into local configuration space
67 * device's configuration space.
76 * rio_local_read_config_16 - Read 16 bits from local configuration space
78 * @offset: Offset into local configuration space
82 * device's configuration space.
91 * rio_local_write_config_16 - Write 16 bits to local configuration space
[all …]
|
| /openbmc/openbmc/meta-fii/meta-mori/recipes-kernel/linux/linux-nuvoton/ |
| H A D | mori.cfg | 1 # Sensors Configuration
17 # IIO Configuration
23 # LEDs Configuration
32 # FS Configuration
39 # SPI Configuration
45 # Network Configuration
54 # I2C Configuration
73 # JATG Configuration
77 # Core Netfilter Configuration
91 # IP: Netfilter Configuration
[all …]
|
| /openbmc/docs/designs/ |
| H A D | voltage-regulator-configuration.md | 1 # Voltage Regulator Configuration
13 voltage, over-current limit, and pgood thresholds. The configuration is often
15 configuration that is defined by hardware engineers early in system design.
16 However, this default configuration sometimes must be modified by firmware. A
22 ### Regulator Configuration Data ("Config File")
24 Hardware engineers must specify many low-level configuration values for a
30 configuration values into a tool that produces a "config file".
32 The regulator configuration information is sent to manufacturing and stored in
34 default configuration.
36 The default configuration values often need to be changed later. This can be due
[all …]
|
| /openbmc/openbmc-test-automation/redfish/account_service/ |
| H A D | test_ldap_configuration.robot | 2 Documentation Test Redfish LDAP user configuration.
26 Verify LDAP Configuration Created
27 [Documentation] Verify that LDAP configuration created.
30 Create LDAP Configuration
31 # Call 'Get LDAP Configuration' to verify that LDAP configuration exists.
32 Get LDAP Configuration ${LDAP_TYPE}
109 Verify LDAP Configuration Exist
110 [Documentation] Verify that LDAP configuration is available.
115 Should Not Be Empty ${resp} msg=LDAP configuration is not defined.
130 @{ldap_configuration}= Get LDAP Configuration ${LDAP_TYPE}
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-connectivity/thingsboard-gateway/thingsboard-gateway/ |
| H A D | tb_gateway.yaml | 20 configuration: mqtt.json
25 # configuration: modbus.json
30 # configuration: modbus_serial.json
35 # configuration: opcua.json
40 # configuration: ble.json
45 # configuration: request.json
50 # configuration: can.json
55 # configuration: bacnet.json
60 # configuration: odbc.json
65 # configuration: custom_serial.json
|
| /openbmc/linux/tools/testing/kunit/test_data/ |
| H A D | test_is_test_passed-no_tests_run_no_header.log | 40 setup_one_line failed for device 1 : Configuration failed
42 setup_one_line failed for device 2 : Configuration failed
44 setup_one_line failed for device 3 : Configuration failed
46 setup_one_line failed for device 4 : Configuration failed
48 setup_one_line failed for device 5 : Configuration failed
50 setup_one_line failed for device 6 : Configuration failed
52 setup_one_line failed for device 7 : Configuration failed
54 setup_one_line failed for device 8 : Configuration failed
56 setup_one_line failed for device 9 : Configuration failed
58 setup_one_line failed for device 10 : Configuration failed
[all …]
|
| /openbmc/phosphor-webui/app/configuration/ |
| H A D | index.js | 2 * A module for the configuration
4 * @module app/configuration/index
5 * @exports app/configuration/index
12 .module('app.configuration', ['ngRoute', 'app.common.services'])
13 // Route configuration
18 .when('/configuration/network', {
23 .when('/configuration/date-time', {
28 .when('/configuration', {
33 .when('/configuration/snmp', {
38 .when('/configuration/firmware', {
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 3 Hardware modules that control pin multiplexing or configuration parameters
8 Hardware modules whose signals are affected by pin configuration are
14 single static pin configuration, e.g. set up during initialization. Others
22 configuration used by those states.
26 driver loads. This would allow representing a board's static pin configuration
31 they require certain specific named states for dynamic pin configuration.
37 property exists to define the pin configuration. Each state may also be
47 pinctrl-0: List of phandles, each pointing at a pin configuration
48 node. These referenced pin configuration nodes must be child
53 contributing part of the overall configuration. See the next
[all …]
|
| /openbmc/u-boot/drivers/usb/gadget/ |
| H A D | core.c | 77 "GET CONFIGURATION", /* 8 */
78 "SET CONFIGURATION", /* 9 */
126 * usbd_device_configuration_instance - find a configuration instance for this device
128 * @configuration: index to configuration, 0 - N-1
130 * Get specifed device configuration. Index should be bConfigurationValue-1.
133 unsigned int port, unsigned int configuration) in usbd_device_configuration_instance() argument
135 if (configuration >= device->configurations) in usbd_device_configuration_instance()
138 return device->configuration_instance_array + configuration; in usbd_device_configuration_instance()
145 * @configuration: index to configuration, 0 - N-1
150 …interface_instance (struct usb_device_instance *device, int port, int configuration, int interface) in usbd_device_interface_instance() argument
[all …]
|
| /openbmc/linux/drivers/net/ipa/ |
| H A D | ipa_data.h | 16 * DOC: IPA/GSI Configuration Data
18 * Boot-time configuration data is used to define the configuration of the
26 * configuration data defines the number (or limits of the number) of various
29 * Endpoint configuration data defines properties of both IPA endpoints and
40 * added. IPA endpoint and GSI channel configuration data are defined
43 * Endpoint configuration data consists of three parts: properties that
52 /** enum ipa_qsb_master_id - array index for IPA QSB configuration data */
59 * struct ipa_qsb_data - Qualcomm System Bus configuration data
71 * struct gsi_channel_data - GSI channel configuration data
99 * struct ipa_endpoint_data - IPA endpoint configuration data
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/tools/ |
| H A D | validate-regulators-config.py | 11 Validates the phosphor-regulators configuration file. Checks it against a JSON
24 To search the entire configuration file, pass the root JSON element
47 Get all rule IDs in the configuration file.
48 config_json: Configuration file JSON
58 Get all device IDs in the configuration file.
59 config_json: Configuration file JSON
72 config_json: Configuration file JSON
110 config_json: Configuration file JSON
129 config_json: Configuration file JSON
148 config_json: Configuration file JSON
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/ |
| H A D | README.md | 6 regulators. The application is controlled by a JSON configuration file.
14 The configuration of voltage regulators can be modified. Configuration changes
17 The most common configuration change is setting the output voltage for a
21 The configuration changes are applied early in the boot process before
49 ## JSON Configuration File
51 The JSON configuration file defines the following:
54 - Operations to perform on those regulators, such as configuration or sensor
57 Configuration files are stored in the `config_files` directory.
59 See the [configuration file documentation](docs/config_file/README.md) for
|
| /openbmc/linux/include/linux/dma/ |
| H A D | sprd-dma.h | 76 * configuration into one reserved memory, then DMA can fetch each DMA
77 * configuration automatically to start transfer.
102 * @SPRD_DMA_CFGERR_INT: configure error interrupt when configuration is
126 * can supply several groups configurations (each configuration represents one
128 * configurations by writing the physical address of each configuration into the
132 * physical address of 'configuration 1', and the 'configuration 1' link-list
133 * pointer will be pointed to 'configuration 2', and so on.
134 * Once trigger the DMA transfer, the DMA controller will load 'configuration
135 * 1' to its registers automatically, after 'configuration 1' transaction is
136 * done, DMA controller will load 'configuration 2' automatically, until all
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | smsc47b397.rst | 104 Configuration Sequence
107 To program the configuration registers, the following sequence must be followed:
108 1. Enter Configuration Mode
109 2. Configure the Configuration Registers
110 3. Exit Configuration Mode.
112 Enter Configuration Mode
115 To place the chip into the Configuration State The config key (0x55) is written
118 Configuration Mode
121 In configuration mode, the INDEX PORT is located at the CONFIG PORT address and
124 The desired configuration registers are accessed in two steps:
[all …]
|