| /openbmc/linux/Documentation/hwmon/ |
| H A D | ibmpowernv.rst | 18 'hwmon' populates the 'sysfs' tree having attribute files, each for a given
21 All the nodes in the DT appear under "/ibm,opal/sensors" and each valid node in
45 each OCC. Using this attribute each OCC can be asked to
58 each OCC. Using this attribute each OCC can be asked to
69 each OCC. Using this attribute each OCC can be asked to
80 each OCC. Using this attribute each OCC can be asked to
|
| /openbmc/linux/drivers/net/ethernet/qlogic/qlcnic/ |
| H A D | qlcnic_dcb.c | 570 struct qlcnic_dcb_param *each; in qlcnic_83xx_dcb_query_cee_param() local
597 each = &mbx_out.type[j]; in qlcnic_83xx_dcb_query_cee_param()
599 each->hdr_prio_pfc_map[0] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
600 each->hdr_prio_pfc_map[1] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
601 each->prio_pg_map[0] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
602 each->prio_pg_map[1] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
603 each->pg_bw_map[0] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
604 each->pg_bw_map[1] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
605 each->pg_tsa_map[0] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
606 each->pg_tsa_map[1] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
[all …]
|
| /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/linux/tools/testing/selftests/firmware/ |
| H A D | settings | 2 # 2 seconds). There are 3 test configs, each done with and without firmware
3 # present, each with 2 "nowait" functions tested 5 times. Expected time for a
5 # Additionally, fw_fallback may take 5 seconds for internal timeouts in each
7 # 10 seconds for each testing config: 120 + 15 + 30
|
| /openbmc/linux/tools/perf/tests/shell/ |
| H A D | stat_bpf_counters_cgrp.sh | 15 if ! perf stat -a --bpf-counters --for-each-cgroup / true > /dev/null 2>&1; then
18 perf --no-pager stat -a --bpf-counters --for-each-cgroup / true || true
51 …check_system_wide_counted_output=$(perf stat -a --bpf-counters --for-each-cgroup ${test_cgroups} -…
63 …check_cpu_list_counted_output=$(perf stat -C 0,1 --bpf-counters --for-each-cgroup ${test_cgroups} …
|
| /openbmc/linux/scripts/ |
| H A D | find-unused-docs.sh | 44 for each in "${files_included[@]}"; do
45 FILES_INCLUDED[$each]="$each"
|
| /openbmc/linux/Documentation/devicetree/bindings/phy/ |
| H A D | apm-xgene-phy.txt | 19 Two set of 3-tuple setting for each (up to 3)
25 Two set of 3-tuple setting for each (up to 3)
28 gain control. Two set of 3-tuple setting for each
32 each (up to 3) supported link speed on the host.
36 3-tuple setting for each (up to 3) supported link
40 3-tuple setting for each (up to 3) supported link
46 - apm,tx-speed : Tx operating speed. One set of 3-tuple for each
|
| /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/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-max3191x.txt | 18 - maxim,modesel-gpios: GPIO pins to configure modesel of each chip.
20 (if each chip is driven by a separate pin) or 1
22 - maxim,fault-gpios: GPIO pins to read fault of each chip.
25 - maxim,db0-gpios: GPIO pins to configure debounce of each chip.
28 - maxim,db1-gpios: GPIO pins to configure debounce of each chip.
|
| /openbmc/linux/Documentation/devicetree/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
|
| /openbmc/linux/Documentation/filesystems/nfs/ |
| H A D | pnfs.rst | 6 reference multiple devices, each of which can reference multiple data servers.
20 We reference the header for the inode pointing to it, across each
22 LAYOUTCOMMIT), and for each lseg held within.
34 nfs4_deviceid_cache). The cache itself is referenced across each
36 the lifetime of each lseg referencing them.
66 layout types: "files", "objects", "blocks", and "flexfiles". For each
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-detect.rst | 37 - The image is divided into a grid, each cell with its own motion
41 - The image is divided into a grid, each cell with its own region
55 Sets the motion detection thresholds for each cell in the grid. To
61 Sets the motion detection region value for each cell in the grid. To
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | map_cgroup_storage.rst | 127 per-CPU variant will have different memory regions for each CPU for each
128 storage. The non-per-CPU will have the same memory region for each storage.
133 multiple attach types, and each attach creates a fresh zeroed storage. The
136 There is a one-to-one association between the map of each type (per-CPU and
138 each map can only be used by one BPF program and each BPF program can only use
139 one storage map of each type. Because of map can only be used by one BPF
153 However, the BPF program can still only associate with one map of each type
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/4xx/ |
| H A D | cpm.txt | 16 - unused-units : specifier consist of one cell. For each
20 - idle-doze : specifier consist of one cell. For each
24 - standby : specifier consist of one cell. For each
28 - suspend : specifier consist of one cell. For each
|
| /openbmc/linux/Documentation/cpu-freq/ |
| H A D | cpufreq-stats.rst | 22 cpufreq-stats is a driver that provides CPU frequency statistics for each CPU.
25 in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU.
65 This gives the amount of time spent in each of the frequencies supported by
66 this CPU. The cat output will have "<frequency> <time>" pair in each line, which
68 will have one line for each of the supported frequencies. usertime units here
100 also contains the actual freq values for each row and column for better
|
| /openbmc/linux/Documentation/leds/ |
| H A D | leds-qcom-lpg.rst | 16 channels. The output of each PWM channel is routed to other hardware
19 The each PWM channel can operate with a period between 27us and 384 seconds and
37 therefore be identical for each element in the pattern (except for the pauses
39 transitions expected by the leds-trigger-pattern format, each entry in the
73 mode, in which case each run through the pattern is performed by first running
|
| /openbmc/linux/tools/power/cpupower/ |
| H A D | TODO | 17 -> Bind forked process to each cpu.
19 each cpu.
22 each cpu.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | procfs-smaps_rollup | 7 except instead of an entry for each VMA in a process,
9 for which each field is the sum of the corresponding
13 the sum of the Pss field of each type (anon, file, shmem).
|
| /openbmc/linux/Documentation/admin-guide/mm/damon/ |
| H A D | usage.rst | 60 figure, parents-children relations are represented with indentations, each
61 directory is having ``/`` suffix, and files in each directory are separated by
109 are called DAMON context. DAMON executes each context with a kernel thread
115 of child directories named ``0`` to ``N-1``. Each directory represents each
121 In each kdamond directory, two files (``state`` and ``pid``) and one directory
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
138 operating scheme action tried regions directory for each DAMON-based operation
153 ``0`` to ``N-1``. Each directory represents each monitoring context. At the
162 In each context directory, two files (``avail_operations`` and ``operations``)
[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-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/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/linux/Documentation/networking/ |
| H A D | scaling.rst | 30 applying a filter to each packet that assigns it to one of a small number
31 of logical flows. Packets for each flow are steered to a separate receive
41 implementation of RSS uses a 128-entry indirection table where each entry
60 for each CPU if the device supports enough queues, or otherwise at least
61 one for each memory domain, where a memory domain is a set of CPUs that
79 that can route each interrupt to a particular CPU. The active mapping
84 affinity of each interrupt see Documentation/core-api/irq/irq-affinity.rst. Some systems
100 interrupts (and thus work) grows with each additional queue.
103 processors with hyperthreading (HT), each hyperthread is represented as
141 RPS may enqueue packets for processing. For each received packet,
[all …]
|
| /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/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
|