Searched full:on (Results 1 – 25 of 3245) sorted by relevance
12345678910>>...130
| /Documentation/devicetree/bindings/regulator/ |
| D | pfuze100.txt | 10 regulators (e.g. DDR ref, DDR supply) has set the "regulator-always-on"
11 property. If not present, the switched regulators are always on and can't be
13 old dtb's which rely on the fact that the switched regulators are always on
14 and don't mark them explicit as "regulator-always-on".
18 management IC (PMIC) on PMIC_STBY_REQ signal.
48 regulator-boot-on;
49 regulator-always-on;
56 regulator-boot-on;
57 regulator-always-on;
63 regulator-boot-on;
[all …]
|
| D | tps65090.txt | 54 regulator-boot-on;
55 regulator-always-on;
62 regulator-boot-on;
63 regulator-always-on;
68 regulator-boot-on;
69 regulator-always-on;
74 regulator-boot-on;
75 regulator-always-on;
80 regulator-boot-on;
81 regulator-always-on;
[all …]
|
| D | tps65217.txt | 15 - ti,pmic-shutdown-controller: Telling the PMIC to shutdown on PWR_EN toggle.
32 regulator-boot-on;
33 regulator-always-on;
39 regulator-boot-on;
40 regulator-always-on;
46 regulator-boot-on;
47 regulator-always-on;
53 regulator-boot-on;
54 regulator-always-on;
60 regulator-boot-on;
[all …]
|
| D | ltc3589.txt | 16 Required properties (not on ldo3, ldo4):
24 regulator is fixed to 1.8 V on LTC3589 and to 2.8 V on LTC3589-1,2. The ldo4
25 regulator can output between 1.8 V and 3.3 V on LTC3589 and between 1.2 V
26 and 3.2 V on LTC3589-1,2 in four steps. The ldo1 standby regulator can not
27 be disabled and thus should have the regulator-always-on property set.
41 regulator-boot-on;
42 regulator-always-on;
50 regulator-boot-on;
51 regulator-always-on;
59 regulator-boot-on;
[all …]
|
| D | mt6380-regulator.txt | 25 regulator-always-on;
26 regulator-boot-on;
41 regulator-always-on;
42 regulator-boot-on;
50 regulator-always-on;
51 regulator-boot-on;
59 regulator-always-on;
60 regulator-boot-on;
68 regulator-always-on;
69 regulator-boot-on;
[all …]
|
| D | ltc3676.txt | 16 Required properties (not on ldo3):
26 regulator can not be disabled and thus should have the regulator-always-on
41 regulator-boot-on;
42 regulator-always-on;
50 regulator-boot-on;
51 regulator-always-on;
59 regulator-boot-on;
60 regulator-always-on;
68 regulator-boot-on;
69 regulator-always-on;
[all …]
|
| D | tps65218.txt | 31 regulator-boot-on;
32 regulator-always-on;
39 regulator-boot-on;
40 regulator-always-on;
47 regulator-boot-on;
48 regulator-always-on;
55 regulator-boot-on;
56 regulator-always-on;
63 regulator-boot-on;
64 regulator-always-on;
[all …]
|
| D | pv88060.txt | 32 regulator-boot-on;
39 regulator-boot-on;
46 regulator-boot-on;
53 regulator-boot-on;
60 regulator-boot-on;
67 regulator-boot-on;
74 regulator-boot-on;
81 regulator-boot-on;
94 regulator-boot-on;
101 regulator-boot-on;
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | sunxi.txt | 11 "allwinner,sun6i-a31-pll1-clk" - for the main PLL clock on A31
12 "allwinner,sun8i-a23-pll1-clk" - for the main PLL clock on A23
13 "allwinner,sun4i-a10-pll3-clk" - for the video PLL clock on A10
14 "allwinner,sun9i-a80-pll4-clk" - for the peripheral PLLs on A80
17 "allwinner,sun6i-a31-pll6-clk" - for the PLL6 clock on A31
18 "allwinner,sun9i-a80-gt-clk" - for the GT bus clock on A80
21 "allwinner,sun8i-a23-axi-clk" - for the AXI clock on A23
22 "allwinner,sun4i-a10-gates-clk" - for generic gates on all compatible SoCs
25 "allwinner,sun5i-a13-ahb-clk" - for the AHB clock on A13
26 "allwinner,sun9i-a80-ahb-clk" - for the AHB bus clocks on A80
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | renesas,sdhi.txt | 5 "renesas,sdhi-sh73a0" - SDHI IP on SH73A0 SoC
6 "renesas,sdhi-r7s72100" - SDHI IP on R7S72100 SoC
7 "renesas,sdhi-r7s9210" - SDHI IP on R7S9210 SoC
8 "renesas,sdhi-r8a73a4" - SDHI IP on R8A73A4 SoC
9 "renesas,sdhi-r8a7740" - SDHI IP on R8A7740 SoC
10 "renesas,sdhi-r8a7743" - SDHI IP on R8A7743 SoC
11 "renesas,sdhi-r8a7744" - SDHI IP on R8A7744 SoC
12 "renesas,sdhi-r8a7745" - SDHI IP on R8A7745 SoC
13 "renesas,sdhi-r8a774a1" - SDHI IP on R8A774A1 SoC
14 "renesas,sdhi-r8a774c0" - SDHI IP on R8A774C0 SoC
[all …]
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 8 # The recursive limitations with Kconfig has some non intuitive implications on
12 # annotate those requirements, ie, some drivers use "depends on" while others
14 # core requirement, and one uses "select" while the other uses "depends on" to
18 # A perhaps not so obvious implication of this is that, if semantics on these
20 # they select or depend on end up becoming shared requirements which cannot be
31 # due to the disjoint use of semantics on expressing each bell's relationship
32 # with CORE, one uses "depends on" while the other uses "select". Another
35 # as mandatory required symbols. For more details on the heavy handed nature
38 # To fix this the "depends on CORE" must be changed to "select CORE", or the
39 # "select CORE" must be changed to "depends on CORE".
[all …]
|
| D | kconfig-language.rst | 20 | +- Set version information on all module symbols
35 bool "Set version information on all module symbols"
36 depends on MODULES
58 tristate and string; the other types are based on these two. The type
117 - dependencies: "depends on" <expr>
129 depends on BAR
147 if FOO depends on BAR that is not set.
150 That will limit the usefulness but on the other hand avoid
155 This is similar to "select" as it enforces a lower limit on another
167 depends on BAR
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | v3-v360epc-pci.txt | 13 as routed on the system.
28 on the Integrator, some registers in the syscon are required to
56 0x4800 0 0 1 &pic 13 /* INT A on slot 9 is irq 13 */
57 0x4800 0 0 2 &pic 14 /* INT B on slot 9 is irq 14 */
58 0x4800 0 0 3 &pic 15 /* INT C on slot 9 is irq 15 */
59 0x4800 0 0 4 &pic 16 /* INT D on slot 9 is irq 16 */
61 0x5000 0 0 1 &pic 14 /* INT A on slot 10 is irq 14 */
62 0x5000 0 0 2 &pic 15 /* INT B on slot 10 is irq 15 */
63 0x5000 0 0 3 &pic 16 /* INT C on slot 10 is irq 16 */
64 0x5000 0 0 4 &pic 13 /* INT D on slot 10 is irq 13 */
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | rk808.txt | 172 regulator-always-on;
173 regulator-boot-on;
180 regulator-always-on;
181 regulator-boot-on;
188 regulator-always-on;
189 regulator-boot-on;
194 regulator-always-on;
195 regulator-boot-on;
202 regulator-always-on;
203 regulator-boot-on;
[all …]
|
| D | tps6507x.txt | 19 If some of input supply is powered through battery or always-on
21 node handle of always on power supply.
52 regulator-always-on;
53 regulator-boot-on;
60 regulator-always-on;
61 regulator-boot-on;
69 regulator-always-on;
70 regulator-boot-on;
78 regulator-always-on;
79 regulator-boot-on;
[all …]
|
| /Documentation/sound/hd-audio/ |
| D | models.rst | 59 Disable HP EAPD on NID 0x15
61 Enable SPDIF output on NID 0x1e
84 GPIO LED support on HP laptops
98 Combo jack sensing on ALC283
136 Mute LED via Mic1 pin on HP
138 Mute LED via Mic2 pin on HP
140 Mute LED via Mic3 pin on HP
142 GPIO + Mic1 pin LED on HP
144 Mute LED via Line1 + Mic1 pins on HP
160 Limit internal mic boost on Lenovo machines
[all …]
|
| /Documentation/ |
| D | robust-futex-ABI.txt | 9 futexes, for kernel assist of cleanup of held locks on task exit.
11 The interesting data as to what futexes a thread is holding is kept on a
25 threads in the kernel. Options on the sys_futex(2) system call support
26 waiting on a particular futex, and waking up the next waiter on a
32 to do so, then improperly listed locks will not be cleaned up on exit,
34 waiting on the same locks.
43 consisting of three words. Each word is 32 bits on 32 bit arch's, or 64
44 bits on 64 bit arch's, and local byte order. Each thread should have
47 If a thread is running in 32 bit compatibility mode on a 64 native arch
51 compatibility mode, will attempt to process both lists on each task
[all …]
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | mpc8xxx-wdt.txt | 10 On the 83xx, "Watchdog Timer Registers" area: <0x200 0x100>
11 On the 86xx, "Watchdog Timer Registers" area: <0xe4000 0x100>
12 On the 8xx, "General System Interface Unit" area: <0x0 0x10>
16 Reset Status Register (called RSTRSCR on the mpc86xx)
17 On the 83xx, it is located at offset 0x910
18 On the 86xx, it is located at offset 0xe0094
19 On the 8xx, it is located at offset 0x288
|
| /Documentation/networking/ |
| D | arcnet-hardware.txt | 27 100 Mbps card to a 2.5 Mbps card, and so on. From what I hear, my driver does
64 limit on their packet sizes; standard ARCnet can only send packets that are
71 For more information on the advantages and disadvantages (mostly the
127 2. A card to a passive hub. Remember that all unused connectors on the hub
136 doesn't limit the number of active hubs on the network.
158 uses 50 Ohm impedance. You use T connectors to put the computers on a single
208 the empty connectors of cards on the ends of the chain. An example:
218 involved in using them; you just connect a TP chain to a hub on any end or
220 The maximum of 11 hubs between any two computers on the net applies here as
256 - the I/O address: this is the "port" your ARCnet card is on. Probed
[all …]
|
| /Documentation/hwmon/ |
| D | max6639.rst | 49 temp1_max_alarm R Alarm on THERM temperature on channel 1
50 temp2_max_alarm R Alarm on THERM temperature on channel 2
51 temp1_crit_alarm R Alarm on ALERT temperature on channel 1
52 temp2_crit_alarm R Alarm on ALERT temperature on channel 2
53 temp1_emergency_alarm R Alarm on OT temperature on channel 1
54 temp2_emergency_alarm R Alarm on OT temperature on channel 2
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 6 Locking scheme used for directory operations is based on two
10 When taking the i_rwsem on multiple non-directory objects, we
74 (1) if object removal or non-cross-directory rename holds lock on A and
75 attempts to acquire lock on B, A will remain the parent of B until we
76 acquire the lock on B. (Proof: only cross-directory rename can change
79 (2) if cross-directory rename holds the lock on filesystem, order will not
81 renames will be blocked on filesystem lock and we don't start changing
84 (3) locks on non-directory objects are acquired only after locks on
86 (Proof: all operations but renames take lock on at most one
87 non-directory object, except renames, which take locks on source and
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | dev-subdev.rst | 31 will feature a character device node on which ioctls can be called to
37 - negotiate image formats on individual pads
59 behave identically as when issued on V4L2 device nodes, with the
63 Depending on the driver, those controls might also be exposed through
71 :ref:`event`. The API behaves identically as when used on V4L2 device
73 the sub-device. Depending on the driver, those events might also be
74 reported on one (or several) V4L2 device nodes.
94 Image formats are typically negotiated on video capture and output
102 hardware configurations. One such example is shown on
103 :ref:`pipeline-scaling`, where image scaling can be performed on both
[all …]
|
| /Documentation/fb/ |
| D | s3fb.rst | 17 - probably not working on big endian
19 I tested s3fb on Trio64 (plain, V+ and V2/DX) and Virge (plain, VX, DX),
20 all on i386.
29 * 24 bpp truecolor mode (RGB 888) on (only on Virge VX)
30 * 32 bpp truecolor mode (RGB 888) on (not on Virge VX)
39 lower pixclocks (maximum usually between 50-60 MHz, depending on specific
43 support is broken on S3 Trio64 V2/DX.
50 Suspend/resume works on systems that initialize video card during resume and
62 * 24 bpp mode support on more cards
78 * text mode broken on S3 Trio64 V2/DX
|
| /Documentation/devicetree/bindings/bus/ |
| D | ts-nbus.txt | 4 Systems FPGA on the TS-4600 SoM.
11 - ts,data-gpios : The 8 GPIO pins connected to the data lines on the FPGA
12 - ts,csn-gpios : The GPIO pin connected to the csn line on the FPGA
13 - ts,txrx-gpios : The GPIO pin connected to the txrx line on the FPGA
14 - ts,strobe-gpios : The GPIO pin connected to the stobe line on the FPGA
15 - ts,ale-gpios : The GPIO pin connected to the ale line on the FPGA
16 - ts,rdy-gpios : The GPIO pin connected to the rdy line on the FPGA
21 on the bus.
|
| /Documentation/powerpc/ |
| D | vcpudispatch_stats.txt | 7 on their associated physical processor chip. However, under certain
8 scenarios, vcpus may be dispatched on a different processor chip (away
26 2. number of times this vcpu was dispatched on the same processor as last
28 3. number of times this vcpu was dispatched on a different processor core
30 4. number of times this vcpu was dispatched on a different chip
31 5. number of times this vcpu was dispatches on a different socket/drawer
61 statistics were enabled. 4126 of those dispatches were on the same
62 physical cpu as the last time. 2683 were on a different core, but within
63 the same chip, while 30 dispatches were on a different chip compared to
67 6821 dispatches on the vcpu's home node, while 18 dispatches were
[all …]
|
12345678910>>...130