Home
last modified time | relevance | path

Searched +full:0 +full:x1ff (Results 1 – 11 of 11) sorted by relevance

/Documentation/devicetree/bindings/thermal/
Dthermal-sensor.yaml35 0 on sensor nodes with only a single sensor and at least 1 on nodes
37 enum: [0, 1]
57 reg = <0 0x0c263000 0 0x1ff>, /* TM */
58 <0 0x0c222000 0 0x1ff>; /* SROT */
68 reg = <0 0x0c265000 0 0x1ff>, /* TM */
69 <0 0x0c223000 0 0x1ff>; /* SROT */
Dthermal-zones.yaml68 checking this thermal zone. Setting this to 0 disables the polling
77 this to 0 disables the polling timers setup by the thermal
134 "^[a-zA-Z][a-zA-Z0-9\\-_]{0,63}$":
254 reg = <0 0x0c263000 0 0x1ff>, /* TM */
255 <0 0x0c222000 0 0x1ff>; /* SROT */
265 reg = <0 0x0c265000 0 0x1ff>, /* TM */
266 <0 0x0c223000 0 0x1ff>; /* SROT */
Dqcom-tsens.yaml127 - pattern: '^s[0-9]+_p1$'
128 - pattern: '^s[0-9]+_p2$'
129 - pattern: '^s[0-9]+_p1$'
130 - pattern: '^s[0-9]+_p2$'
131 - pattern: '^s[0-9]+_p1$'
132 - pattern: '^s[0-9]+_p2$'
133 - pattern: '^s[0-9]+_p1$'
134 - pattern: '^s[0-9]+_p2$'
135 - pattern: '^s[0-9]+_p1$'
136 - pattern: '^s[0-9]+_p2$'
[all …]
/Documentation/devicetree/bindings/phy/
Dsamsung,exynos5250-sata-phy.yaml26 const: 0
58 reg = <0x12170000 0x1ff>;
61 #phy-cells = <0>;
/Documentation/devicetree/bindings/ata/
Dsnps,dwc-ahci.yaml37 "^sata-port@[0-9a-e]$":
56 reg = <0x122F0000 0x1ff>;
58 #size-cells = <0>;
68 ports-implemented = <0x1>;
70 sata-port@0 {
71 reg = <0>;
/Documentation/devicetree/bindings/mailbox/
Dxlnx,zynqmp-ipi-mailbox.yaml48 - "smc" : SMC #0, following the SMCCC
49 - "hvc" : HVC #0, following the SMCCC
80 '^mailbox@[0-9a-f]+$':
107 It contains tx(0) or rx(1) channel IPI id number.
190 #address-cells = <0x2>;
191 #size-cells = <0x2>;
195 xlnx,ipi-id = <0>;
202 reg = <0x0 0xff9905c0 0x0 0x20>,
203 <0x0 0xff9905e0 0x0 0x20>,
204 <0x0 0xff990e80 0x0 0x20>,
[all …]
/Documentation/devicetree/bindings/usb/
Domap-usb.txt12 interface between the controller and the phy. It should be "0" or "1"
73 reg = <0x4a020000 0x1ff>;
74 interrupts = <0 93 4>;
/Documentation/networking/device_drivers/ethernet/aquantia/
Datlantic.rst100 PHYAD: 0
126 version: 5.2.0-050200rc5-generic-kern
151 InErrors: 0
168 InDroppedDma: 0
169 Queue[0] InPackets: 23567131
170 Queue[0] OutPackets: 20070028
171 Queue[0] InJumboPackets: 0
172 Queue[0] InLroPackets: 0
173 Queue[0] InErrors: 0
176 Queue[1] InJumboPackets: 0
[all …]
/Documentation/fb/
Dsisfb.rst89 number in decimal or hexadecimal. For example: vesa=791 or vesa=0x117. Please
145 vesa:X selects startup videomode. X is number from 0 to 0x1FF and
147 hexadecimal form, the latter prefixed with "0x").
Dmatroxfb.rst31 pass to the kernel this command line: "video=matroxfb:vesa:0x1BB".
35 unless you have primary display on non-Matrox VBE2.0 device (see
48 4 0x12 0x102
49 8 0x100 0x101 0x180 0x103 0x188
50 15 0x110 0x181 0x113 0x189
51 16 0x111 0x182 0x114 0x18A
52 24 0x1B2 0x184 0x1B5 0x18C
53 32 0x112 0x183 0x115 0x18B
63 4 0x104 0x106
64 8 0x105 0x190 0x107 0x198 0x11C
[all …]
/Documentation/bpf/
Dverifier.rst72 stack bounds, which are [-MAX_BPF_STACK, 0). In this example offset is 8,
78 Classic BPF verifier does similar check with M[0-15] memory slots.
164 1s in the value represent bits known to be 1. Bits known to be 0 have 0 in both
167 the low 8 are unknown - which is represented as the tnum (0x0; 0xff). If we
168 then OR this with 0x40, we get (0x40; 0xbf), then if we add 1 we get (0x0;
169 0x1ff), because of potential carries.
219 R1=ctx R3=pkt(id=0,off=0,r=14) R4=pkt_end R5=pkt(id=0,off=14,r=14) R10=fp
226 as R3=pkt(id=0,off=0,r=14).
227 id=0 means that no additional variables were added to the register.
228 off=0 means that no additional constants were added.
[all …]