Searched full:corresponding (Results 1 – 25 of 707) sorted by relevance
12345678910>>...29
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-sgi_uv | 68 The cnode entry contains the cnode number of the corresponding hub.
71 The location entry contains the location string of the corresponding hub.
74 The name entry contains the name of the corresponding hub. This name can
85 The nasid entry contains the nasid number of the corresponding hub.
89 corresponding hub is shared between system partitions.
92 the corresponding hub is local to the current partition.
95 each representing a fabric port on the corresponding hub.
137 the corresponding PCI bus address. Known possible values
148 of the CPU physically connected to the corresponding PCI bus.
151 corresponding PCI bus. This value is used to physically locate
[all …]
|
| D | sysfs-devices-platform-sh_mobile_lcdc_fb | 5 This file is only available on fb[0-9] devices corresponding
16 This file is only available on fb[0-9] devices corresponding
29 This file is only available on fb[0-9] devices corresponding
39 This file is only available on fb[0-9] devices corresponding
|
| D | sysfs-class-devfreq | 15 of the corresponding devfreq object.
22 governor used by the corresponding devfreq object.
29 frequency of the corresponding devfreq object. Same as
38 predicted target frequency of the corresponding devfreq object.
63 the available frequencies of the corresponding devfreq object.
99 the requested polling interval of the corresponding devfreq
|
| D | sysfs-bus-intel_th-output-devices | 13 Description: (RO) Port number, corresponding to this output device on the
14 switch (GTH) or "unassigned" if the corresponding output
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | cpm.txt | 17 bit in the cell, the corresponding bit
21 bit in the cell, the corresponding bit
25 bit in the cell, the corresponding bit
29 bit in the cell, the corresponding bit
32 and suspend the corresponding bits can
|
| /Documentation/accounting/ |
| D | delay-accounting.rst | 26 important tasks could be a trigger for raising its corresponding priority.
30 thread group (corresponding to a traditional Unix process). This is a commonly
44 generic data structure to userspace corresponding to per-pid and per-tgid
57 experienced by the task waiting for the corresponding resource
66 commands to be run and the corresponding delay statistics to be displayed. It
91 executed and the corresponding delays to be
|
| /Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,k3-sci-common.yaml | 20 of properties that enables them to implement the corresponding functionality
34 Should contain the TI-SCI device id corresponding to the device. Please
35 refer to the corresponding System Controller documentation for valid
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | zii,rave-sp-backlight.txt | 3 RAVE SP backlight device is a "MFD cell" device corresponding to
6 corresponding to the parent RAVE SP device (as documented in
|
| /Documentation/devicetree/bindings/input/ |
| D | zii,rave-sp-pwrbutton.txt | 3 RAVE SP input device is a "MFD cell" device corresponding to power
6 corresponding to the parent RAVE SP device (as documented in
|
| /Documentation/hwmon/ |
| D | max127.rst | 33 in[0-7]_input The input voltage (in mV) of the corresponding channel.
36 in[0-7]_min The lower input limit (in mV) for the corresponding channel.
41 in[0-7]_max The higher input limit (in mV) for the corresponding channel.
|
| D | ina3221.rst | 36 corresponding alarm when the respective current
40 corresponding alarm when the respective current
50 measurements, activates the corresponding alarm
|
| D | max197.rst | 58 in[0-7]_input The conversion value for the corresponding channel.
61 in[0-7]_min The lower limit (in mV) for the corresponding channel.
66 in[0-7]_max The higher limit (in mV) for the corresponding channel.
|
| /Documentation/driver-api/ |
| D | tee.rst | 14 iterates over the client driver UUID table to find a corresponding
16 probed via corresponding probe API registered by the client driver. This
25 is left open for TEE drivers to provide corresponding implementation.
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 20 and map one to one to corresponding commands.
30 such as BPF program or BPF map. They're represented by corresponding
35 provided via corresponding getters and setters rather than directly.
37 These objects are associated with corresponding parts of ELF object that
47 For example ``bpf_object__open`` consists of the name of corresponding
52 All objects and corresponding functions other than BTF related should go
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | zii,rave-sp-wdt.txt | 3 RAVE SP watchdog device is a "MFD cell" device corresponding to
6 corresponding to the parent RAVE SP device (as documented in
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | power-mgt.txt | 80 indicating which psscr fields are set in the corresponding
86 only the Requested Level (RL) field of the corresponding entry
103 psscr fields of the corresponding entry in
109 register value is to be set in pmicr for the corresponding
116 which of the fields of the PMICR are set in the corresponding
|
| /Documentation/devicetree/bindings/spi/ |
| D | nvidia,tegra210-quad-peripheral-props.yaml | 18 QSPI to corresponding slave device.
27 QSPI to corresponding slave device.
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices | 10 an of_path symlink pointing to the corresponding device
31 Major and minor numbers of the character device corresponding
|
| /Documentation/devicetree/bindings/regulator/ |
| D | mps,mpq7920.yaml | 35 switching frequency must be one of following corresponding value
59 corresponding values 150us, 300us, 610us, 920us
66 corresponding values 0deg, 90deg, 180deg, 270deg
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti,gpmc-child.yaml | 28 # Chip-select signal timings corresponding to GPMC_CONFIG2:
41 # ADV signal timings corresponding to GPMC_CONFIG3:
66 # WE signals timings corresponding to GPMC_CONFIG4:
75 # OE signals timings corresponding to GPMC_CONFIG4:
92 # Access time and cycle time timings (in nanoseconds) corresponding to
|
| /Documentation/trace/coresight/ |
| D | coresight-trbe.rst | 14 memory, CPU traces generated from a corresponding percpu tracing unit. This
15 gets plugged in as a coresight sink device because the corresponding trace
|
| /Documentation/devicetree/bindings/net/ |
| D | ethernet-phy.yaml | 128 Mark the corresponding energy efficient ethernet mode as
134 Mark the corresponding energy efficient ethernet mode as
140 Mark the corresponding energy efficient ethernet mode as
146 Mark the corresponding energy efficient ethernet mode as
152 Mark the corresponding energy efficient ethernet mode as
158 Mark the corresponding energy efficient ethernet mode as
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 80 corresponding frame to the matching capture buffer.
129 of macroblocks to decode a full corresponding frame to the matching
170 of macroblocks to decode a full corresponding frame to the matching
193 of macroblocks to decode a full corresponding frame to the matching
222 number of macroblocks to decode a full corresponding frame.
274 of macroblocks to decode a full corresponding frame to the matching
|
| /Documentation/RCU/Design/Data-Structures/ |
| D | Data-Structures.rst | 138 are protected by the corresponding root ``rcu_node`` structure's lock.
140 #. The fields in ``rcu_data`` are private to the corresponding CPU,
175 to the corresponding leaf ``rcu_node`` structure to allow
179 access to this information from the corresponding CPU. Finally, this
180 structure records past dyntick-idle state for the corresponding CPU
244 structure on the corresponding level of the tree, for example, as shown
260 corresponding CPU's ``rcu_data`` structure.
350 one bit set. This mask is used to clear the bit corresponding to this
396 period request seen by the corresponding ``rcu_node`` structure. The
433 corresponding bit. Note that the leaf ``rcu_node`` structures should be
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | nvidia,tegra210-sfc.yaml | 50 to corresponding ACIF output port on AHUB (Audio Hub).
56 SFC ACIF output port. This is connected to corresponding ACIF
|
12345678910>>...29