| /openbmc/u-boot/drivers/pinctrl/renesas/ |
| H A D | Kconfig | 16 the GPIO definitions and pin control functions for each available
26 the GPIO definitions and pin control functions for each available
36 the GPIO definitions and pin control functions for each available
46 the GPIO definitions and pin control functions for each available
56 the GPIO definitions and pin control functions for each available
66 the GPIO definitions and pin control functions for each available
76 the GPIO definitions and pin control functions for each available
86 the GPIO definitions and pin control functions for each available
96 the GPIO definitions and pin control functions for each available
106 the GPIO definitions and pin control functions for each available
|
| /openbmc/u-boot/doc/device-tree-bindings/gpu/ |
| H A D | nvidia,tegra20-host1x.txt | 14 - resets: Must contain an entry for each entry in reset-names.
19 The host1x top-level node defines a number of children, each representing one
30 - resets: Must contain an entry for each entry in reset-names.
43 - resets: Must contain an entry for each entry in reset-names.
56 - resets: Must contain an entry for each entry in reset-names.
69 - resets: Must contain an entry for each entry in reset-names.
82 - resets: Must contain an entry for each entry in reset-names.
92 - clocks: Must contain an entry for each entry in clock-names.
99 - resets: Must contain an entry for each entry in reset-names.
111 - clocks: Must contain an entry for each entry in clock-names.
[all …]
|
| /openbmc/pldm/libpldmresponder/examples/events/ |
| H A D | event_state_sensor.json | 2 // entry for each sensor in a composite sensor) and the supported event states.
5 // for each corresponding entry in the "event_states"
|
| /openbmc/pldm/libpldmresponder/test/pdr_jsons/state_sensor/malformed/ |
| H A D | sensor_pdr.json | 7 // Each sensor in each group of composite sensors has a separate entry and the
11 // for each corresponding entry in the "states".
|
| /openbmc/pldm/libpldmresponder/examples/pdr/ |
| H A D | sensor_pdr.json | 7 // Each sensor in each group of composite sensors has a separate entry and the
11 // for each corresponding entry in the "states".
|
| /openbmc/sdbusplus/include/sdbusplus/server/ |
| H A D | README.md | 6 name and message cookie from a dbus call. The bus name (unique to each
7 application) and message cookie (unique within each bus peer) allows each dbus
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/js/ |
| H A D | newcustomimage_modal.js | 40 $(".radio").each(function(){
58 $(".radio").each(function(){
196 imageSelectRadiosContainer.find("input:radio").each(function(){
|
| /openbmc/u-boot/doc/device-tree-bindings/sound/ |
| H A D | intel-hda.txt | 3 Configuration is set using 'verbs' which are blocks of 16 bytes of data each
25 - verbs: List of verbs, each 4 cells in length
|
| /openbmc/u-boot/doc/device-tree-bindings/pmic/ |
| H A D | max77686.txt | 17 To bind each regulator, the optional regulators subnode should exists.
20 - voltage-regulators: subnode list of each device's regulator
|
| H A D | sandbox.txt | 20 To bind each regulator, the optional regulator subnodes should exists.
23 - ldo/buck subnodes of each device's regulator (see regulator binding info)
|
| /openbmc/openbmc-test-automation/xcat/ |
| H A D | test_xcat_group.robot | 35 # Power on each BMC node and validate the power status.
45 # Power off each BMC node and validate the power status.
78 # Validate power status on each BMC node one by one.
99 # Validate power status on each BMC node one by one.
137 # Get temperature reading from each BMC node.
155 # Get fanspeed from each BMC node.
171 # Get voltage reading from each BMC node.
186 # Get wattage reading from each BMC node.
|
| /openbmc/u-boot/doc/device-tree-bindings/misc/ |
| H A D | intel-lpc.txt | 12 cell pairs can be provided - the first of each pair is the base address and
20 - intel,pirq-routing : Speciffies the routing IRQ number for each of PIRQA-H,
21 one cell for each.
|
| /openbmc/u-boot/drivers/pinctrl/ |
| H A D | Kconfig | 27 It is totally up to the implementation of each low-level driver.
52 allows the required function to be selected for each pin.
115 both the GPIO definitions and pin control functions for each
132 feature on each I/O pin.
146 Supports individual pin selection and configuration for each
158 the GPIO definitions and pin control functions for each available
168 both the GPIO definitions and pin control functions for each
199 the GPIO definitions and pin control functions for each available
209 the GPIO definitions and pin control functions for each available
|
| /openbmc/qemu/qapi/ |
| H A D | stats.json | 31 # for each power of two.
121 # @target: the kind of objects to query. Note that each possible
125 # optionally which named values to return within each provider
191 # Returns: a list of statistics, one for each provider and object
192 # (e.g., for each vCPU).
206 # @name: name of the statistic; each element of the schema is uniquely
225 # width of each bucket of the histogram.
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | boot_utils.robot | 2 Documentation This module provides one wrapper keyword for each kind of boot
13 # stack_mode If stack_mode is set to "skip", each test
39 # stack_mode If stack_mode is set to "skip", each test
65 # stack_mode If stack_mode is set to "skip", each test
91 # stack_mode If stack_mode is set to "skip", each test
117 # stack_mode If stack_mode is set to "skip", each test
143 # stack_mode If stack_mode is set to "skip", each test
169 # stack_mode If stack_mode is set to "skip", each test
196 # stack_mode If stack_mode is set to "skip", each test
222 # stack_mode If stack_mode is set to "skip", each test
[all …]
|
| /openbmc/openbmc/poky/documentation/profile-manual/ |
| H A D | arch.rst | 27 Rather than enumerating here how each tool makes use of these common
29 in each tool as they come up in the course of the text.
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 26 address space, each of which access the same underlying state. See the hardware
32 a number of GPIOs. Thus, each GPIO is named according to an alphabetical port
36 The number of ports implemented by each GPIO controller varies. The number of
37 implemented GPIOs within each port varies. GPIO registers within a controller
54 Each GPIO controller in fact generates multiple interrupts signals for each set
56 interrupt signals generated by a set-of-ports. The intent is for each generated
57 signal to be routed to a different CPU, thus allowing different CPUs to each
58 handle subsets of the interrupts within a port. The status of each of these
|
| /openbmc/u-boot/doc/device-tree-bindings/pwm/ |
| H A D | pwm.txt | 16 PWM properties should be named "pwms". The exact meaning of each pwms
17 property must be documented in the device tree binding for each device.
19 each of the PWM devices listed in the "pwms" property. If no "pwm-names"
|
| /openbmc/u-boot/doc/device-tree-bindings/i2c/ |
| H A D | i2c-mux.txt | 5 multiplexer/switch will have one child node for each child
26 with two NXP pca8574 GPIO expanders attached, one each to
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libdata/ |
| H A D | libdata-hexdump-perl_0.02.bb | 4 in the source in the leftmost column of each line, followed by one or \
6 of each line shows the printable characters \
|
| /openbmc/openbmc/poky/meta/conf/machine/include/ |
| H A D | README | 17 with the machine configuration, or each other in a multilib
32 tuning ends up with features which conflict with each other.
38 specific tune. This is a list of features that a tune support, each
59 See each architecture's README for details for that CPU family.
64 each architecture. See each architectures README for details for that
|
| /openbmc/u-boot/doc/device-tree-bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 9 designated client devices. Again, each client device must be represented as a
16 device is inactive. Hence, each client device can define a set of named
35 For each client device individually, every pin state is assigned an integer
36 ID. These numbers start at 0, and are contiguous. For each state ID, a unique
47 pinctrl-0: List of phandles, each pointing at a pin configuration
52 from multiple nodes for a single pin controller, each
65 pinctrl-1: List of phandles, each pointing at a pin configuration
68 pinctrl-n: List of phandles, each pointing at a pin configuration
120 The contents of each of those pin configuration child nodes is defined
|
| /openbmc/phosphor-modbus/mocked_test_device/ |
| H A D | Readme.md | 13 accepts a count parameter and starts a separate mocked Modbus server for each
16 pseudo-terminals (PTYs) and initiates a `mock-modbus-device` instance for each
|
| /openbmc/openbmc/poky/bitbake/doc/sphinx-static/ |
| H A D | switchers.js | 63 $.each(all_versions, function(version, title) {
85 $.each(all_doctypes, function(doctype, title) {
224 $.each(all_versions, function(version, title) {
|
| /openbmc/u-boot/doc/device-tree-bindings/reset/ |
| H A D | reset.txt | 23 the DT node of each affected HW block, since if activated, an unrelated block
29 rather than to slavishly enumerate the reset signal that affects each HW
49 for each reset signal that affects the device, or that the
73 This represents a bus that controls the reset signal of each of four sub-
|