| /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/Documentation/trace/coresight/ |
| H A D | coresight-config.rst | 38 CoreSight device is registered with the configuration manager.
78 configuration may be selected.
81 to support system configuration. A configuration may select features to be
112 1) In this example, the configuration is 'autofdo', which has an
116 configuration as part of its command line::
120 which will enable the 'autofdo' configuration.
222 a hash of the configuration name.
249 In a configuration there are 'enable' and 'preset' files.
251 To enable a configuration for use with sysfs::
263 This will select preset3 for the configuration.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/lm_sensors/ |
| H A D | lmsensors-config_1.0.bb | 1 SUMMARY = "lm_sensors configuration files"
2 DESCRIPTION = "Hardware health monitoring configuration files"
23 # Install fancontrol configuration file
27 # Install libsensors configuration file
32 # Install sensord configuration file
43 # libsensors configuration
46 # sensord logging daemon configuration
49 # fancontrol script configuration
58 # libsensors configuration file
61 # sensord logging daemon configuration files
[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
14 entity manager configuration file and schema file names must be
17 ## A single entity manager configuration
27 The type property identifies the type of the configuration. When exported,
28 configuration data will be instantiated as grandchildren of
35 configuration data will be instantiated as children of
43 the configuration to DBus, making it available to other applications.
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/sdk/ |
| H A D | testsdk.py | 15 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/u-boot/drivers/usb/gadget/ |
| H A D | core.c | 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()
154 …if ((configuration_instance = usbd_device_configuration_instance (device, port, configuration)) ==… in usbd_device_interface_instance()
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
235 …if (!(interface_instance = usbd_device_interface_instance (device, port, configuration, interface)… in usbd_device_interface_descriptor()
256 *device, int port, int configuration, int interface, int alternate, int index) in usbd_device_endpoint_descriptor_index() argument
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | configuration_tests.cpp | 68 EXPECT_EQ(configuration.getVolts().value(), 1.3); in TEST()
69 EXPECT_EQ(configuration.getActions().size(), 2); in TEST()
81 EXPECT_EQ(configuration.getActions().size(), 1); in TEST()
112 std::unique_ptr<Configuration> configuration = in TEST() local
122 std::move(configuration)); in TEST()
172 std::unique_ptr<Configuration> configuration = in TEST() local
182 std::move(configuration)); in TEST()
239 std::unique_ptr<Configuration> configuration = in TEST() local
249 std::move(configuration)); in TEST()
297 std::unique_ptr<Configuration> configuration = in TEST() local
[all …]
|
| H A D | device_tests.cpp | 128 auto configuration = in TEST_F() local
150 std::move(configuration), in TEST_F()
185 std::move(configuration), in TEST_F()
515 auto configuration = in TEST_F() local
532 auto configuration = in TEST_F() local
547 auto configuration = in TEST_F() local
559 std::move(configuration), in TEST_F()
609 std::move(configuration), in TEST_F()
673 std::move(configuration), in TEST_F()
701 auto configuration = in TEST_F() local
[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
27 just placing configurations in a ``local.conf`` configuration file
33 - *Create the distribution configuration file:* The distribution
34 configuration file needs to be created in the ``conf/distro``
50 Your configuration file needs to set the following required
58 from the distribution configuration file:
70 If you want to base your distribution configuration file on the
71 very basic configuration from OE-Core, you can use
80 of the distribution configuration. You can include nearly any
95 - Add recipes for installing distro-specific configuration files
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-support/nvmetcli/ |
| H A D | nvmetcli_0.7.bb | 1 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/phosphor-virtual-sensor/ |
| H A D | README.md | 3 phosphor-virtual-sensor reads the configuration file
14 ## virtual sensor configuration information
19 ## information to get a virtual sensor configuration from D-Bus
35 The virtual sensor configuration information needs to be added into the relevant
36 hardware configuration file in entity-manager. This method of adding a virtual
38 different virtual sensors for each configuration.
40 The virtual sensor configuration in entity manager follows a different format to
|
| /openbmc/openbmc/poky/bitbake/lib/bb/ |
| H A D | monitordisk.py | 128 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/phosphor-power/phosphor-regulators/src/ |
| H A D | rail.hpp | 62 std::unique_ptr<Configuration> configuration = nullptr, in Rail() argument
65 configuration{std::move(configuration)},
103 return configuration; in getConfiguration()
153 std::unique_ptr<Configuration> configuration{}; member in phosphor::power::regulators::Rail
|
| /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
22 configuration used by those states.
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
55 pin configuration nodes.
65 pinctrl-1: List of phandles, each pointing at a pin configuration
68 pinctrl-n: List of phandles, each pointing at a pin configuration
90 * For an IP block whose binding supports pin configuration,
[all …]
|
| H A D | sprd,pinctrl.txt | 7 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-power/phosphor-regulators/docs/config_file/ |
| H A D | rail.md | 19 …configuration | no | [configuration](configuration.md) | Specifies configuration…
28 "configuration": {
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/mycroft/files/ |
| H A D | 0007-mycroft.conf-Use-pocketsphinx-by-default.patch | 12 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 D | n_gsm.rst | 51 struct termios configuration;
71 /* get n_gsm extended configuration */
77 /* get n_gsm configuration */
85 /* set the new configuration */
87 /* get DLC 1 configuration */
148 struct termios configuration;
161 /* get n_gsm extended configuration */
165 /* set the new extended configuration */
167 /* get n_gsm configuration */
175 /* set the new configuration */
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-magnetometer-hmc5843 | 6 Current configuration and available configurations
11 positivebias Positive bias configuration
12 negativebias Negative bias configuration
18 The effect of this configuration may vary
|
| /openbmc/phosphor-power/phosphor-regulators/ |
| H A D | README.md | 4 regulators. The application is controlled by a JSON configuration file.
12 The configuration of voltage regulators can be modified. Configuration changes
15 The most common configuration change is setting the output voltage for a
19 The configuration changes are applied early in the boot process before
49 The JSON configuration file defines the following:
52 - Operations to perform on those regulators, such as configuration or sensor
57 See the [configuration file documentation](docs/config_file/README.md) for
|
| /openbmc/u-boot/doc/device-tree-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
22 configuration used by those states.
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
55 pin configuration nodes.
65 pinctrl-1: List of phandles, each pointing at a pin configuration
90 * For an IP block whose binding supports pin configuration,
159 == Generic pin configuration node content ==
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.rockchip | 33 - EVB RK3288 - use evb-rk3288 configuration
42 - Radxa Rock 2 - use rock2 configuration
49 - Kylin - use kylin_rk3036 configuration
59 - Puma - use puma_rk3399 configuration
60 - Ficus - use ficus-rk3399 configuration
62 - Bob - use chromebook_bob configuration
66 - Sheep - use sheep-rk3368 configuration
67 - Lion - use lion-rk3368 configuration
68 - Geekbox - use geekbox configuration
69 - EVB PX5 - use evb-px5 configuration
[all …]
|
| /openbmc/u-boot/drivers/pinctrl/mscc/ |
| H A D | Kconfig | 12 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
|
| /openbmc/linux/Documentation/networking/dsa/ |
| H A D | b53.rst | 26 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`
56 single port and gateway configuration, while there is no need to add an extra
57 VLAN configuration in the bridge showcase.
[all …]
|
| /openbmc/obmc-console/ |
| H A D | CHANGELOG.md | 22 1. config: Added support for the `aspeed-uart-routing` configuration key
23 2. config: Added support for the `ringbuffer-size` configuration key
28 2. config: Drop support for the `socket-id` configuration key
32 1. console-server: Fix configuration of lpc_address and sirq sysfs attributes
50 2. console-server: Don't require a configuration file
59 Deprecate the `socket-id` key in the configuration schema. Uses of
|