Home
last modified time | relevance | path

Searched refs:configuration (Results 1 – 25 of 2927) sorted by relevance

12345678910>>...118

/openbmc/linux/Documentation/trace/coresight/
H A Dcoresight-config.rst26 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.
86 This will define the features that must be enabled as part of the configuration
95 that the configuration uses. The number of values in a single preset set, equals
[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/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 …]
/openbmc/phosphor-power/phosphor-regulators/test/
H A Dconfiguration_tests.cpp66 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()
112 std::unique_ptr<Configuration> configuration = in TEST() local
114 Configuration* configurationPtr = configuration.get(); in TEST()
122 std::move(configuration)); in TEST()
[all …]
H A Ddevice_tests.cpp128 auto configuration = in TEST_F() local
150 std::move(configuration), in TEST_F()
171 std::unique_ptr<Configuration> configuration{}; in TEST_F() local
185 std::move(configuration), in TEST_F()
257 std::unique_ptr<Configuration> configuration{}; in TEST_F() local
258 auto rail = std::make_unique<Rail>("vdd", std::move(configuration), in TEST_F()
451 std::unique_ptr<Configuration> configuration{}; in TEST_F() local
458 configuration = in TEST_F()
469 std::move(configuration)}; in TEST_F()
515 auto configuration = in TEST_F() local
[all …]
/openbmc/u-boot/drivers/usb/gadget/
H A Dcore.c133 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()
150 …interface_instance (struct usb_device_instance *device, int port, int configuration, int interface) in usbd_device_interface_instance() argument
154 …if ((configuration_instance = usbd_device_configuration_instance (device, port, configuration)) ==… in usbd_device_interface_instance()
172 …alternate_instance (struct usb_device_instance *device, int port, int configuration, int interface… in usbd_device_alternate_instance() argument
176 …if ((interface_instance = usbd_device_interface_instance (device, port, configuration, interface))… in usbd_device_alternate_instance()
211 *device, int port, int configuration) in usbd_device_configuration_descriptor() argument
214 if (!(configuration_instance = usbd_device_configuration_instance (device, port, configuration))) { in usbd_device_configuration_descriptor()
232 *device, int port, int configuration, int interface, int alternate) in usbd_device_interface_descriptor() argument
[all …]
/openbmc/openbmc/poky/meta/lib/oeqa/sdk/
H A Dtestsdk.py15 configuration = {'TEST_TYPE': test_type,
23 return configuration
26 def get_sdk_result_id(configuration): argument
27 …s_%s_%s' % (configuration['TEST_TYPE'], configuration['IMAGE_BASENAME'], configuration['SDKMACHINE…
129 configuration = self.get_sdk_configuration(d, self.test_type)
131 configuration,
132 self.get_sdk_result_id(configuration))
/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 …]
/openbmc/openbmc/poky/bitbake/lib/bb/
H A Dmonitordisk.py128 def getInterval(configuration): argument
136 interval = configuration.getVar("BB_DISKMON_WARNINTERVAL")
169 def __init__(self, configuration): argument
172 self.configuration = configuration
174 BBDirs = configuration.getVar("BB_DISKMON_DIRS") or None
178 self.spaceInterval, self.inodeInterval = getInterval(configuration)
226 … bb.event.fire(bb.event.DiskFull(dev, 'disk', freeSpace, path), self.configuration)
231 … bb.event.fire(bb.event.DiskFull(dev, 'disk', freeSpace, path), self.configuration)
253 … bb.event.fire(bb.event.DiskFull(dev, 'inode', freeInode, path), self.configuration)
258 … bb.event.fire(bb.event.DiskFull(dev, 'inode', freeInode, path), self.configuration)
[all …]
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A Dpinctrl-bindings.txt3 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 …]
H A Dsprd,pinctrl.txt7 to configure for some global common configuration, such as domain
15 There are too much various configuration that we can not list all
16 of them, so we can not make every Spreadtrum-special configuration
17 as one generic configuration, and maybe it will add more strange
18 global configuration in future. Then we add one "sprd,control" to
19 set these various global control configuration, and we need use
30 configuration.
34 related configuration are:
43 configuration, to set the pin sleep related configuration automatically
46 and set the pin sleep related configuration as "input-enable", which
/openbmc/phosphor-virtual-sensor/
H A DREADME.md3 phosphor-virtual-sensor reads the configuration file
14 ## virtual sensor configuration information
19 ## information to get a virtual sensor configuration from D-Bus
34 The virtual sensor configuration information needs to be added into the relevant
35 hardware configuration file in entity-manager. This method of adding a virtual
37 different virtual sensors for each configuration.
39 The virtual sensor configuration in entity manager follows a different format to
/openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-support/nvmetcli/
H A Dnvmetcli_0.8.bb1 SUMMARY = "NVM-Express target user space configuration utility."
4 interactively as well as saving / restoring the configuration to / from a json \
11 # nvmet service will start and stop the NVMe Target configuration on boot and
12 # shutdown from a saved NVMe Target configuration in the /etc/nvmet/config.json
13 # file. This file is not installed by default since the configuration will vary
14 # on real systems. Example configuration files are provided by including the
28 # Install example configuration scripts.
/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
107 exposes record in the json configuration
109 - When a device is detected as present using the GPIO configuration published by
111 entity-manager to publish the associated configuration.
136 %% initial base configuration
[all …]
/openbmc/phosphor-power/phosphor-regulators/src/
H A Drail.hpp62 std::unique_ptr<Configuration> configuration = nullptr, in Rail() argument
64 id{id}, configuration{std::move(configuration)}, in Rail()
102 return configuration; in getConfiguration()
152 std::unique_ptr<Configuration> configuration{}; member in phosphor::power::regulators::Rail
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/
H A Drail.md19 …configuration | no | [configuration](configuration.md) | Specifies configuration…
28 "configuration": {
H A Ddevice.md9 - Voltage regulators that require configuration or monitoring.
23 …configuration | no | [configuration](configuration.md) | Specifies c…
39 "configuration": {
/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/mycroft/files/
H A D0007-mycroft.conf-Use-pocketsphinx-by-default.patch12 mycroft/configuration/mycroft.conf | 2 +-
15 diff --git a/mycroft/configuration/mycroft.conf b/mycroft/configuration/mycroft.conf
17 --- a/mycroft/configuration/mycroft.conf
18 +++ b/mycroft/configuration/mycroft.conf
/openbmc/linux/Documentation/driver-api/tty/
H A Dn_gsm.rst51 struct termios configuration;
71 /* get n_gsm extended configuration */
75 /* set the new extended configuration */
77 /* get n_gsm configuration */
85 /* set the new configuration */
87 /* get DLC 1 configuration */
92 /* set the new DLC 1 specific configuration */
148 struct termios configuration;
161 /* get n_gsm extended configuration */
165 /* set the new extended configuration */
[all …]
/openbmc/u-boot/doc/
H A DREADME.rockchip33 - EVB RK3288 - use evb-rk3288 configuration
34 - Fennec RK3288 - use fennec-rk3288 configuration
35 - Firefly RK3288 - use firefly-rk3288 configuration
36 - Hisense Chromebook - use chromebook_jerry configuration
37 - Asus C100P Chromebook - use chromebook_minnie configuration
38 - Asus Chromebit - use chromebook_mickey configuration
39 - MiQi RK3288 - use miqi-rk3288 configuration
40 - phyCORE-RK3288 RDK - use phycore-rk3288 configuration
41 - PopMetal RK3288 - use popmetal-rk3288 configuration
42 - Radxa Rock 2 - use rock2 configuration
[all …]
/openbmc/u-boot/doc/device-tree-bindings/pinctrl/
H A Dpinctrl-bindings.txt3 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/linux/Documentation/networking/dsa/
H A Db53.rst26 The configuration of the device depends on whether or not tagging is
29 The interface names and example network configuration are used according the
30 configuration described in the :ref:`dsa-config-showcases`.
35 The tagging based configuration is desired. It is not specific to the b53
38 See :ref:`dsa-tagged-configuration`.
46 switch need a different configuration.
48 The configuration slightly differ from the :ref:`dsa-vlan-configuration`.
54 In difference to the configuration described in :ref:`dsa-vlan-configuration`
55 the default VLAN 1 has to be removed from the slave interface configuration in
56 single port and gateway configuration, while there is no need to add an extra
[all …]
/openbmc/phosphor-power/phosphor-regulators/
H A DREADME.md6 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
51 The JSON configuration file defines the following:
54 - Operations to perform on those regulators, such as configuration or sensor
59 See the [configuration file documentation](docs/config_file/README.md) for
/openbmc/qemu/docs/interop/
H A Dqemu-ga.rst25 qemu-ga will read a system configuration file on startup (located at
27 configuration options on the command line. For the same key, the last
28 option wins, but the lists accumulate (see below for configuration
31 If an allowed RPCs list is defined in the configuration, then all
34 If a blocked RPCs list is defined in the configuration, then all
37 If both allowed and blocked RPCs lists are defined in the configuration,
42 of RPCs will blocked, regardless of what the general configuration
113 Dump the configuration in a format compatible with ``qemu-ga.conf``
124 The syntax of the ``qemu-ga.conf`` configuration file follows the
130 # qemu-ga configuration sample
/openbmc/u-boot/drivers/pinctrl/mscc/
H A DKconfig12 Support pin multiplexing and pin configuration control on
21 Support pin multiplexing and pin configuration control on
30 Support pin multiplexing and pin configuration control on
39 Support pin multiplexing and pin configuration control on
48 Support pin multiplexing and pin configuration control on

12345678910>>...118