| /linux/Documentation/hwmon/ |
| 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
|
| /linux/drivers/net/ethernet/qlogic/qlcnic/ |
| 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()
601 each->prio_pg_map[0] = 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()
607 val = each->hdr_prio_pfc_map[0]; in qlcnic_83xx_dcb_query_cee_param()
611 each->app[i] = cmd.rsp.arg[i + k]; in qlcnic_83xx_dcb_query_cee_param()
656 struct qlcnic_dcb_param *each, in qlcnic_dcb_fill_cee_tc_params() argument
[all …]
|
| /linux/tools/testing/selftests/firmware/ |
| 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
|
| /linux/tools/perf/tests/shell/ |
| 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} …
|
| /linux/scripts/ |
| A D | find-unused-docs.sh | 44 for each in "${files_included[@]}"; do
45 FILES_INCLUDED[$each]="$each"
|
| /linux/Documentation/devicetree/bindings/phy/ |
| 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
|
| A D | phy-tegra194-p2u.yaml | 14 Speed) each interfacing with 12 and 8 P2U instances respectively.
16 each interfacing with 8, 8 and 8 P2U instances respectively.
29 description: Should be the physical address space and length of respective each P2U instance.
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| 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.
|
| /linux/Documentation/core-api/ |
| A D | protection-keys.rst | 19 Pkeys work by dedicating 4 previously Reserved bits in each page table entry to
22 Protections for each key are defined with a per-CPU user-accessible register
24 and Write Disable) for each of 16 keys.
26 Being a CPU register, PKRU is inherently thread-local, potentially giving each
37 Pkeys use 3 bits in each page table entry, to encode a "protection key index",
40 Protections for each key are defined with a per-CPU user-writable system
42 overlay permissions for each protection key index.
45 each thread a different set of protections from every other thread.
|
| /linux/drivers/pinctrl/sophgo/ |
| A D | Kconfig | 20 each pin. This driver can also be built as a module called
31 each pin. This driver can also be built as a module called
42 each pin. This driver can also be built as a module called
53 each pin. This driver can also be built as a module called
|
| /linux/Documentation/filesystems/nfs/ |
| 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
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| 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
|
| /linux/Documentation/userspace-api/media/v4l/ |
| 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
|
| /linux/Documentation/bpf/ |
| 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
|
| /linux/Documentation/devicetree/bindings/powerpc/4xx/ |
| 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
|
| /linux/Documentation/admin-guide/mm/damon/ |
| A D | usage.rst | 60 figure, parents-children relations are represented with indentations, each
121 child directories named ``0`` to ``N-1``. Each directory represents each
143 - ``update_schemes_stats``: Update the contents of stats files for each
157 ``effective_bytes`` files for each DAMON-based operation scheme of the
229 to ``N-1``. Each directory represents each monitoring target.
236 In each target directory, one file (``pid_target``) and one directory
597 Each line of the output represents each monitoring region that each DAMON-based
728 Reading the file also shows the statistics of each scheme. To the file, each
729 of the schemes should be represented in each line in below form::
817 will show each scheme you entered in each line, and the five numbers for the
[all …]
|
| /linux/tools/power/cpupower/ |
| A D | TODO | 17 -> Bind forked process to each cpu.
19 each cpu.
22 each cpu.
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| A D | qcom,rpmh-common.yaml | 17 associated with each execution environment. Provider nodes must point to at
18 least one RPMh device child node pertaining to their RSC and each provider
37 Names for each of the qcom,bcm-voters specified.
|
| /linux/Documentation/ABI/testing/ |
| 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).
|
| /linux/Documentation/devicetree/bindings/iio/adc/ |
| A D | aspeed,ast2600-adc.yaml | 14 • The device split into two individual engine and each contains 8 voltage
18 • Programmable upper and lower threshold for each channels.
19 • Interrupt when larger or less than threshold for each channels.
20 • Support hysteresis for each channels.
|
| /linux/Documentation/leds/ |
| 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
|
| /linux/Documentation/devicetree/bindings/dma/stm32/ |
| A D | st,stm32-mdma.yaml | 13 described in the dma.txt file, using a five-cell specifier for each channel:
24 0x2: Source address pointer is incremented after each data transfer
25 0x3: Source address pointer is decremented after each data transfer
28 0x2: Destination address pointer is incremented after each data transfer
29 0x3: Destination address pointer is decremented after each data transfer
|
| /linux/Documentation/cpu-freq/ |
| 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
|
| /linux/lib/ |
| A D | Kconfig.kasan | 75 See Documentation/dev-tools/kasan.rst for details about each mode.
109 comparison, as it embeds a tag into the top byte of each pointer.
125 comparison, as it embeds a tag into the top byte of each pointer.
138 is accessible before each memory access. Slower than KASAN_INLINE, but
146 each memory access. Faster than KASAN_OUTLINE (gives ~x2 boost for
213 recorded for each heap block at allocation and free time, and
214 8 bytes will be added to each metadata structure that records
217 In Generic KASAN, each kmalloc-8 and kmalloc-16 object will add
218 16 bytes of additional memory consumption, and each kmalloc-32
|
| /linux/Documentation/virt/acrn/ |
| 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
|