Home
last modified time | relevance | path

Searched full:on (Results 1 – 25 of 3289) sorted by relevance

12345678910>>...132

/Documentation/devicetree/bindings/timer/
Drenesas,cmt.yaml28 - renesas,r8a7740-cmt0 # 32-bit CMT0 on R-Mobile A1
29 - renesas,r8a7740-cmt1 # 48-bit CMT1 on R-Mobile A1
30 - renesas,r8a7740-cmt2 # 32-bit CMT2 on R-Mobile A1
31 - renesas,r8a7740-cmt3 # 32-bit CMT3 on R-Mobile A1
32 - renesas,r8a7740-cmt4 # 32-bit CMT4 on R-Mobile A1
33 - renesas,sh73a0-cmt0 # 32-bit CMT0 on SH-Mobile AG5
34 - renesas,sh73a0-cmt1 # 48-bit CMT1 on SH-Mobile AG5
35 - renesas,sh73a0-cmt2 # 32-bit CMT2 on SH-Mobile AG5
36 - renesas,sh73a0-cmt3 # 32-bit CMT3 on SH-Mobile AG5
37 - renesas,sh73a0-cmt4 # 32-bit CMT4 on SH-Mobile AG5
[all …]
/Documentation/devicetree/bindings/regulator/
Dtps65090.txt54 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 …]
Dtps65217.txt15 - 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 …]
Dltc3589.txt16 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 …]
Dnxp,pca9450-regulator.yaml23 #Note: Buck3 removed on PCA9450B and connect with Buck1 on PCA9450C.
106 regulator-boot-on;
107 regulator-always-on;
114 regulator-boot-on;
115 regulator-always-on;
124 regulator-boot-on;
125 regulator-always-on;
131 regulator-boot-on;
132 regulator-always-on;
138 regulator-boot-on;
[all …]
Dpfuze100.yaml44 (e.g. DDR ref, DDR supply) has set the "regulator-always-on" property.
45 If not present, the switched regulators are always on and can't be
47 with old dtb's which rely on the fact that the switched regulators are
48 always on and don't mark them explicit as "regulator-always-on".
56 IC (PMIC) on PMIC_STBY_REQ signal.
99 regulator-boot-on;
100 regulator-always-on;
107 regulator-boot-on;
108 regulator-always-on;
114 regulator-boot-on;
[all …]
Dmt6380-regulator.txt25 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 …]
Dltc3676.txt16 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 …]
Dtps65218.txt31 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 …]
Dpv88060.txt32 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/admin-guide/
Dnumastat.rst11 is incremented on the preferred node, otherwise numa_foreign is incremented on
12 the preferred node and numa_miss on the node where allocation succeeded.
16 counters based on CPU local node. local_node is similar to numa_hit and is
17 incremented on allocation from a node by CPU on the same node. other_node is
18 similar to numa_miss and is incremented on the node where allocation succeeds
31 numa_foreign A process wanted to allocate on this node,
34 local_node A process ran on this node's CPU,
37 other_node A process ran on a different node's CPU
46 well right now on machines with a small number of CPUs.
48 Note that on systems with memoryless nodes (where a node has CPUs but no
[all …]
/Documentation/kbuild/
DKconfig.recursion-issue-028 # 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 …]
Dkconfig-language.rst20 | +- 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/
Dv3-v360epc-pci.txt13 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/
Drk808.txt172 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 …]
Dtps6507x.txt19 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/locking/
Drobust-futex-ABI.rst9 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/sound/hd-audio/
Dmodels.rst59 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/ABI/testing/
Dsysfs-devices-mapping9 For example, on 4-die Xeon platform with up to 6 IIO stacks per
31 IIO PMU 0 on die 0 belongs to PCI RP on bus 0x00, domain 0x0000
32 IIO PMU 0 on die 1 belongs to PCI RP on bus 0x40, domain 0x0000
33 IIO PMU 0 on die 2 belongs to PCI RP on bus 0x80, domain 0x0000
34 IIO PMU 0 on die 3 belongs to PCI RP on bus 0xc0, domain 0x0000
/Documentation/networking/
Darcnet-hardware.rst31 100 Mbps card to a 2.5 Mbps card, and so on. From what I hear, my driver does
68 limit on their packet sizes; standard ARCnet can only send packets that are
75 For more information on the advantages and disadvantages (mostly the
136 2. A card to a passive hub. Remember that all unused connectors on the hub
146 doesn't limit the number of active hubs on the network.
168 uses 50 Ohm impedance. You use T connectors to put the computers on a single
218 the empty connectors of cards on the ends of the chain. An example::
228 involved in using them; you just connect a TP chain to a hub on any end or
230 The maximum of 11 hubs between any two computers on the net applies here as
268 - the I/O address: this is the "port" your ARCnet card is on. Probed
[all …]
/Documentation/devicetree/bindings/watchdog/
Dmpc8xxx-wdt.txt10 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/filesystems/
Ddirectory-locking.rst6 Locking scheme used for directory operations is based on two
10 When taking the i_rwsem on multiple non-directory objects, we
77 (1) if object removal or non-cross-directory rename holds lock on A and
78 attempts to acquire lock on B, A will remain the parent of B until we
79 acquire the lock on B. (Proof: only cross-directory rename can change
82 (2) if cross-directory rename holds the lock on filesystem, order will not
84 renames will be blocked on filesystem lock and we don't start changing
87 (3) locks on non-directory objects are acquired only after locks on
89 (Proof: all operations but renames take lock on at most one
90 non-directory object, except renames, which take locks on source and
[all …]
/Documentation/hwmon/
Dmax6639.rst49 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/userspace-api/media/v4l/
Ddev-subdev.rst24 will feature a character device node on which ioctls can be called to
30 - negotiate image formats on individual pads
57 behave identically as when issued on V4L2 device nodes, with the
61 Depending on the driver, those controls might also be exposed through
69 :ref:`event`. The API behaves identically as when used on V4L2 device
71 the sub-device. Depending on the driver, those events might also be
72 reported on one (or several) V4L2 device nodes.
92 Image formats are typically negotiated on video capture and output
100 hardware configurations. One such example is shown on
101 :ref:`pipeline-scaling`, where image scaling can be performed on both
[all …]
/Documentation/fb/
Ds3fb.rst17 - 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

12345678910>>...132