| /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/linux/Documentation/admin-guide/mm/damon/ |
| H A D | usage.rst | 60 figure, parents-children relations are represented with indentations, each
109 are called DAMON context. DAMON executes each context with a kernel thread
129 for each DAMON-based operation scheme of the kdamond. For details of the
133 DAMON-based operation scheme action tried regions directory for each
212 to ``N-1``. Each directory represents each monitoring target.
217 In each target directory, one file (``pid_target``) and one directory
453 In each region directory, you will find four files (``start``, ``end``,
613 Reading the file also shows the statistics of each scheme. To the file, each
614 of the schemes should be represented in each line in below form::
704 will show each scheme you entered in each line, and the five numbers for the
[all …]
|
| /openbmc/openbmc-test-automation/xcat/ |
| H A D | test_xcat_group.robot | 36 # Power on each BMC node and validate the power status.
47 # Power off each BMC node and validate the power status.
82 # Validate power status on each BMC node one by one.
104 # Validate power status on each BMC node one by one.
144 # Get temperature reading from each BMC node.
163 # Get fanspeed from each BMC node.
180 # Get voltage reading from each BMC node.
196 # Get wattage reading from each BMC node.
|
| /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/linux/Documentation/virt/acrn/ |
| H A D | io-request.rst | 14 For each User VM, there is a shared 4-KByte memory region used for I/O requests
20 used as an array of 16 I/O request slots with each I/O request slot being 256
27 GPA falls in a certain range. Multiple I/O clients can be associated with each
28 User VM. There is a special client associated with each User VM, called the
30 any other clients. The ACRN userspace acts as the default client for each User
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | nvidia,tegra30-ahub.txt | 8 - reg : Should contain the register physical address and length for each of
13 - clocks : Must contain an entry for each entry in clock-names.
18 - resets : Must contain an entry for each entry in reset-names.
47 - dmas : Must contain an entry for each entry in clock-names.
|
| H A D | wlf,arizona.yaml | 48 A list of boolean values indicating whether each output is mono
64 DMIC reference voltage source for each input, can be selected from
79 The maximum number of channels to be clocked on each AIF, useful for
81 cell for each AIF to be configured, specify zero for AIFs that should
112 The volume limit value that should be applied to each output
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-usb-devices-usbsevseg | 27 raw: each character controls its segment manually
28 hex: each character is between 0-15
29 ascii: each character is between '0'-'9' and 'A'-'F'.
|
| H A D | sysfs-devices-soc | 5 The /sys/devices/ directory contains a sub-directory for each
7 regarding each SoC can be obtained by reading sysfs files. This
10 The directory created for each SoC will also house information
35 or more eight (8) bit fields, each consisting of seven (7)
93 interest, as it contains a symlink for each SoC device found on
|
| /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/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/linux/Documentation/tools/rtla/ |
| H A D | common_osnoise_description.rst | 5 The *osnoise*'s tracer threads take note of the delta between each time
7 At the end of each period, the *osnoise* tracer displays a summary of
|
| /openbmc/linux/Documentation/networking/ |
| H A D | scaling.rst | 30 applying a filter to each packet that assigns it to one of a small number
79 that can route each interrupt to a particular CPU. The active mapping
100 interrupts (and thus work) grows with each additional queue.
141 RPS may enqueue packets for processing. For each received packet,
157 can be configured for each receive queue using a sysfs file entry::
177 receive queue is mapped to each CPU, then RPS is probably redundant
278 for each flow: rps_dev_flow_table is a table specific to each hardware
384 configured for each receive queue by the driver, so no additional
411 (contention can be eliminated completely if each CPU has its own
425 threads are not pinned to CPUs and each thread handles packets
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | amlogic,meson-mx-sdio.txt | 25 A node for each slot provided by the MMC controller is required.
29 Required properties on each child node (= slot):
33 Optional properties on each child node (= slot):
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | marvell,mvebu-pinctrl.txt | 4 (mpp) to a specific function. For each SoC family there is a SoC specific
17 Please refer to each marvell,<soc>-pinctrl.txt binding doc for supported SoCs.
24 valid pin/pin group names and available function names for each SoC.
|
| H A D | fsl,imx-pinctrl.txt | 5 multiplexing the PAD input/output signals. For each PAD there are up to
22 Please refer to each fsl,<soc>-pinctrl.txt binding doc for supported SoCs.
25 - fsl,pins: each entry consists of 6 integers and represents the mux and config
41 Please refer to each fsl,<soc>-pinctrl,txt binding doc for SoC specific part
93 User should refer to each SoC spec to set the correct value.
|
| /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/linux/Documentation/gpu/amdgpu/ |
| H A D | ras.rst | 53 This test checks the RAS availability and enablement status for each supported IP block as well as
58 This test injects errors for each IP.
62 This test tests disabling of RAS features for each IP block.
|
| /openbmc/linux/Documentation/devicetree/bindings/hsi/ |
| H A D | omap-ssi.txt | 11 - reg: Contains a matching register specifier for each entry
14 - interrupts: Contains matching interrupt information for each entry
22 - clocks: Contains a matching clock specifier for each entry in
34 - reg: Contains a matching register specifier for each entry
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | amd-xgbe.txt | 14 interrupt for each DMA channel supported by the device should be specified.
29 a unique interrupt for each DMA channel - this requires an additional
30 interrupt be configured for each DMA channel
38 The following optional properties are represented by an array with each
|
| /openbmc/linux/Documentation/leds/ |
| H A D | leds-class-multicolor.rst | 26 they are defined in each multi_* array file.
42 The brightness level for each LED is calculated based on the color LED
50 for each LED that are necessary to achieve a certain color output from a
71 128 to the global brightness file then the values written to each LED will be
|
| /openbmc/linux/Documentation/devicetree/bindings/mux/ |
| H A D | mux-consumer.yaml | 23 each mux controller property must be documented in the device tree binding for
24 each consumer. An optional property "mux-control-names" may contain a list of
25 strings to label each of the mux controllers listed in the "mux-controls"
31 each of the multiplixer states listed in the "mux-states" property.
|
| /openbmc/linux/tools/memory-model/litmus-tests/ |
| H A D | IRIW+poonceonces+OnceOnce.litmus | 7 * between each pairs of reads. In other words, is anything at all
9 * of a pair of writes, where each write is to a different variable by a
|
| /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/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
|