Searched full:corresponding (Results 1 – 25 of 624) sorted by relevance
12345678910>>...25
| /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/ABI/testing/ |
| 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.
45 the requested polling interval of the corresponding devfreq
82 the available frequencies of the corresponding devfreq object.
|
| 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/accounting/ |
| D | delay-accounting.rst | 22 important tasks could be a trigger for raising its corresponding priority.
26 thread group (corresponding to a traditional Unix process). This is a commonly
40 generic data structure to userspace corresponding to per-pid and per-tgid
52 experienced by the task waiting for the corresponding resource
61 commands to be run and the corresponding delay statistics to be displayed. It
84 executed and the corresponding delays to be
|
| /Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,sci.txt | 30 "rx" - Mailbox corresponding to receive path
31 "tx" - Mailbox corresponding to transmit path
33 - mboxes: Mailboxes corresponding to the mbox-names. Each value of the mboxes
47 - reg: register space corresponding to the debug_messages
49 - ti,host-id: Integer value corresponding to the host ID assigned by Firmware
|
| 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/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/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/display/bridge/ |
| D | renesas,dw-hdmi.txt | 26 version corresponding to the platform first, followed by the
34 corresponding to the video input of the controller and one port numbered 1
35 corresponding to its HDMI output, and one port numbered 2 corresponding to
|
| /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/net/ |
| D | ethernet-phy.yaml | 105 Mark the corresponding energy efficient ethernet mode as
111 Mark the corresponding energy efficient ethernet mode as
117 Mark the corresponding energy efficient ethernet mode as
123 Mark the corresponding energy efficient ethernet mode as
129 Mark the corresponding energy efficient ethernet mode as
135 Mark the corresponding energy efficient ethernet mode as
|
| /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/remoteproc/ |
| D | mtk,scp.txt | 11 - reg-names Contains the corresponding names for the two memory
14 - clock-names Contains the corresponding name for the clock. This
|
| /Documentation/devicetree/bindings/regulator/ |
| D | mps,mpq7920.yaml | 36 switching frequency must be one of following corresponding value
58 corresponding values 150us, 300us, 610us, 920us
65 corresponding values 0deg, 90deg, 180deg, 270deg
|
| /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/hwmon/ |
| 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/devicetree/bindings/mtd/ |
| D | aspeed-smc.txt | 20 - #address-cells : must be 1 corresponding to chip select child binding
21 - #size-cells : must be 0 corresponding to chip select child binding
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | omap-gpmc.txt | 57 Chip-select signal timings (in nanoseconds) corresponding to GPMC_CONFIG2:
62 ADV signal timings (in nanoseconds) corresponding to GPMC_CONFIG3:
70 WE signals timings (in nanoseconds) corresponding to GPMC_CONFIG4:
74 OE signals timings (in nanoseconds) corresponding to GPMC_CONFIG4:
80 Access time and cycle time timings (in nanoseconds) corresponding to
|
| /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/clock/ti/davinci/ |
| D | da8xx-cfgchip.txt | 15 - clocks: phandles to the parent clocks corresponding to clock-names
42 - clocks: phandles to the parent clocks corresponding to clock-names
50 - clocks: phandles to the parent clocks corresponding to clock-names
|
| /Documentation/admin-guide/perf/ |
| D | imx-ddr.rst | 41 - 0: corresponding bit is masked.
42 - 1: corresponding bit is not masked, i.e. used to do the matching.
45 When non-masked bits are matching corresponding AXI_ID bits then counter is
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | battery.yaml | 22 without a corresponding update to the dtb.
24 Battery properties are named, where possible, for the corresponding elements
76 and corresponding battery internal resistance percent, which is used to
114 of the battery and corresponding battery capacity percent, which is used
|
| /Documentation/sound/designs/ |
| D | oss-emulation.rst | 15 corresponding module has to be loaded.
17 These modules are loaded automatically when the corresponding service
38 after the corresponding OSS-emulation module is loaded. Don't worry
266 The second column is the base-string of the corresponding ALSA
282 the base-string of the corresponding ALSA control, and the third the
284 corresponding OSS control is not available.
325 and set the values for the corresponding handle.
|
12345678910>>...25