Home
last modified time | relevance | path

Searched full:configuration (Results 1 – 25 of 5091) sorted by relevance

12345678910>>...204

/openbmc/linux/Documentation/trace/coresight/
Dcoresight-config.rst
/openbmc/u-boot/include/
H A Dfsl_immap.h23 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 Dconfiguration_tests.cpp18 #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 Dmpspec.h22 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/entity-manager/schemas/
H A DREADME.md1 # 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/openbmc/poky/documentation/dev-manual/
H A Dcustom-distribution.rst20 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 …]
H A Dmulticonfig.rst8 different configuration (multiple configuration builds). The builds, in
12 This section describes how to set up for multiple configuration builds
16 Setting Up and Running a Multiple Configuration Build
19 To accomplish a multiple configuration build, you must define each
20 target's configuration separately using a parallel :term:`configuration file` in
21 the :term:`Build Directory` or configuration directory within a layer, and you
23 multiple configuration builds in your ``local.conf`` file.
25 Follow these steps to set up and execute multiple configuration builds:
27 - *Create Separate Configuration Files*: You need to create a single
28 :term:`Configuration File` for each build target (each multiconfig).
[all …]
/openbmc/phosphor-power/phosphor-regulators/docs/
H A Dconfiguration.md1 # Regulator Configuration
5 The configuration of voltage regulators can be modified. Configuration changes
8 The most common configuration change is setting the output voltage for a
12 Regulator configuration occurs early in the system boot before regulators have
15 ## How configuration is defined
17 Configuration is defined for a voltage regulator using the
18 [configuration](config_file/configuration.md) object in the
25 ## How configuration is initiated
31 `phosphor-regulators` will perform the configuration defined in the JSON config
48 If an error occurs while executing actions to perform configuration:
[all …]
H A DREADME.md6 regulators. The application is controlled by a JSON configuration file.
26 The application is driven by a system-specific JSON configuration file. The JSON
28 C++ objects. These objects implement the regulator configuration and monitoring
35 `phosphor-regulators` can modify the configuration of voltage regulators, such
38 See [Regulator Configuration](configuration.md) for more information.
51 ## JSON configuration file
53 The JSON configuration file defines the following:
56 - Operations to perform on those regulators, such as configuration or sensor
59 Configuration files are stored in the [`config_files`](../config_files)
62 See the [configuration file documentation](docs/config_file/README.md) for
/openbmc/phosphor-fan-presence/control/json/
H A Dconfig_base.hpp32 * Configuration object key to uniquely map to the configuration object
34 * std::string = Configuration object's name
35 * std::vector<std::string> = List of profiles the configuration object
41 * @class ConfigBase - Base configuration object
43 * Base class for fan control's JSON configuration objects.
57 // Set the name of this configuration object in ConfigBase()
82 * @brief Get the configuration object's name
84 * @return Name of the configuration object
92 * @brief Get the configuration object's list of profiles
94 * Gets the list of profiles this configuration object belongs to if any
[all …]
/openbmc/u-boot/arch/arm/include/asm/arch-sunxi/
H A Dclock_sun9i.h12 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/docs/designs/inventory/
H A Dgpio-based-hardware-inventory.md40 phosphor-inventory-manager configuration.
49 phosphor-multi-gpio-presence configuration:
61 and phosphor-inventory-manager configuration:
97 configuration
99 - Allow configuration of the detectable inventory items through entity-manager
100 configuration
106 exposes record in the json configuration
108 - When a device is detected as present using the GPIO configuration published by
110 entity-manager to publish the associated configuration.
135 %% initial base configuration
[all …]
/openbmc/openbmc/meta-fii/meta-mori/recipes-kernel/linux/linux-nuvoton/
H A Dmori.cfg1 # 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/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-connectivity/thingsboard-gateway/thingsboard-gateway/
H A Dtb_gateway.yaml20 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/phosphor-power/phosphor-regulators/src/
H A Dconfiguration.hpp37 * @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 Drail.hpp18 #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/phosphor-webui/app/configuration/
H A Dindex.js2 * 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/phosphor-bmc-code-mgmt/i2c-vr/isl69269/
H A Disl69269.cpp297 shiftLeftFromMSB(sepLine + 4, &configuration.devIdExp); in parseImage()
298 debug("device id from configuration: {ID}", "ID", lg2::hex, in parseImage()
299 configuration.devIdExp); in parseImage()
303 shiftLeftFromMSB(sepLine + 4, &configuration.devRevExp); in parseImage()
305 configuration.devRevExp); in parseImage()
312 if (configuration.devRevExp < (gen3SWRevMin << 24)) in parseImage()
315 configuration.mode = gen3Legacy; in parseImage()
320 configuration.mode = gen3Production; in parseImage()
327 configuration.mode = gen2Hex; in parseImage()
346 configuration in parseImage()
[all...]
/openbmc/linux/include/uapi/linux/
Ddcbnl.h
/openbmc/openbmc-test-automation/redfish/managers/
H A Dtest_lldp_config.robot2 Documentation LLDP(Link Layer Discovery Protocol) Test Suite for configuration
22 Set LLDP Configuration State ${True}
25 Verify LLDP Configuration State ${True}
32 Set LLDP Configuration State ${False}
35 Verify LLDP Configuration State ${False}
47 ${initial_lldp_config}= Get Initial LLDP Configuration
50 Set LLDP Configuration State
51 [Documentation] Set LLDP configuration state.
60 Get Initial LLDP Configuration
61 [Documentation] Get initial LLDP configuration.
[all …]
/openbmc/linux/tools/testing/kunit/test_data/
Dtest_is_test_passed-no_tests_run_no_header.log
/openbmc/linux/include/linux/
Drio_drv.h
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-bindings.txt
/openbmc/docs/designs/
H A Dvoltage-regulator-configuration.md1 # 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/meta-openembedded/meta-oe/recipes-bsp/lm_sensors/
H A Dlmsensors-config_1.0.bb1 SUMMARY = "lm_sensors configuration files"
2 DESCRIPTION = "Hardware health monitoring configuration files"
24 # Install fancontrol configuration file
28 # Install libsensors configuration file
33 # Install sensord configuration file
44 # libsensors configuration
47 # sensord logging daemon configuration
50 # fancontrol script configuration
59 # libsensors configuration file
62 # sensord logging daemon configuration files
[all …]

12345678910>>...204