Home
last modified time | relevance | path

Searched full:c0 (Results 1 – 25 of 71) sorted by relevance

123

/Documentation/admin-guide/media/
Ddvb-usb-gp8psk-cardlist.rst16 - 09c0:0200, 09c0:0201
18 - 09c0:0202
20 - 09c0:0203
22 - 09c0:0206
/Documentation/devicetree/bindings/clock/st/
Dst,quadfs.txt37 clk_s_c0_quadfs: clk-s-c0-quadfs@9103000 {
44 clock-output-names = "clk-s-c0-fs0-ch0",
45 "clk-s-c0-fs0-ch1",
46 "clk-s-c0-fs0-ch2",
47 "clk-s-c0-fs0-ch3";
Dst,clkgen-pll.txt14 "st,clkgen-pll0-c0"
16 "st,clkgen-pll1-c0"
Dst,flexgen.txt69 "st,flexgen-stih407-c0"
70 "st,flexgen-stih410-c0"
71 "st,flexgen-stih418-c0"
88 clk_s_c0_flexgen: clk-s-c0-flexgen {
/Documentation/admin-guide/hw-vuln/
Dcross-thread-rsb.rst9 transitions out of C0 state, the other sibling thread could use return target
10 predictions from the sibling thread that transitioned out of C0.
15 transitioning out of C0. This could result in a guest-controlled return target
41 requests to transition out of the C0 state. This can be communicated with the
42 HLT instruction or with an MWAIT instruction that requests non-C0.
43 When the thread re-enters the C0 state, the processor transitions back
44 to 2T mode, assuming the other thread is also still in C0 state.
62 instructions with targeted return locations and then transitioning out of C0
86 attempts to transition out of C0. A VMM can use the KVM_CAP_X86_DISABLE_EXITS
/Documentation/devicetree/bindings/dma/
Dqcom,adm.yaml44 - description: phandle to the c0 reset
52 - const: c0
95 reset-names = "clk", "pbus", "c0", "c1", "c2";
/Documentation/userspace-api/media/v4l/
Dbayer.svg5 …one"/><path id="path208" d="m5250 4400h-650v-1200h1300v1200h-650z" fill="#0c0"/><path id="path210"…
6 …one"/><path id="path225" d="m3950 5600h-650v-1200h1300v1200h-650z" fill="#0c0"/><path id="path227"…
8 …1003"/><path id="path266" d="m5200 6700h-500v-1e3h1e3v1e3h-500z" stroke="#0c0"/></g></g><g id="g26…
11 …one"/><path id="path303" d="m8150 4400h-650v-1200h1300v1200h-650z" fill="#0c0"/><path id="path305"…
12 …one"/><path id="path320" d="m9450 5600h-650v-1200h1300v1200h-650z" fill="#0c0"/><path id="path322"…
16 …ne"/><path id="path384" d="m17950 4400h-650v-1200h1300v1200h-650z" fill="#0c0"/><path id="path386"…
17 …ne"/><path id="path401" d="m16650 5600h-650v-1200h1300v1200h-650z" fill="#0c0"/><path id="path403"…
21 …ne"/><path id="path465" d="m12350 4400h-650v-1200h1300v1200h-650z" fill="#0c0"/><path id="path467"…
22 …ne"/><path id="path482" d="m13650 5600h-650v-1200h1300v1200h-650z" fill="#0c0"/><path id="path484"…
25 …1003"/><path id="path543" d="m6500 5500h-500v-1e3h1e3v1e3h-500z" stroke="#0c0"/></g></g><g id="g54…
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dmarvell,armada-375-pinctrl.txt18 mpp2 2 gpio, dev(ad4), ptp(evreq), led(c0), audio(sdi)
58 mpp42 42 gpio, spi1(cs2), led(c0)
66 mpp50 50 gpio, led(c0), ge0(rxd0), ge1(rxd0)
74 mpp58 58 gpio, led(c0)
/Documentation/devicetree/bindings/soc/fsl/cpm_qe/
Dcpm.txt14 cpm@119c0 {
19 reg = <119c0 30>;
/Documentation/userspace-api/ioctl/
Dioctl-number.rst122 'B' C0-FF advanced bbus <mailto:maassen@uni-freiburg.d…
160 'H' C0-F0 net/bluetooth/hci.h conflict!
161 'H' C0-DF net/bluetooth/hidp/hidp.h conflict!
162 'H' C0-DF net/bluetooth/cmtp/cmtp.h conflict!
163 'H' C0-DF net/bluetooth/bnep/bnep.h conflict!
194 'R' C0-DF net/bluetooth/rfcomm.h
203 'T' C0-DF linux/if_tun.h conflict!
207 'U' C0-CF drivers/bluetooth/hci_uart.h
210 'V' C0 linux/ivtvfb.h conflict!
211 'V' C0 linux/ivtv.h conflict!
[all …]
/Documentation/devicetree/bindings/spi/
Dfsl-spi.txt27 spi@4c0 {
30 reg = <4c0 40>;
/Documentation/arch/x86/
Dzero-page.rst28 0C0/004 ALL ext_ramdisk_image ramdisk_image high 32bits
33 1C0/020 ALL efi_info EFI 32 information (struct efi_info)
/Documentation/hid/
Dhidreport-parsing.rst14 00000030 81 06 c0 c0 |....|
Dhidintro.rst77 00000030 81 06 c0 c0 |....|
194 … 01 75 01 95 03 81 02 75 05 95 01 81 01 05 01 09 30 09 31 09 38 15 81 25 7f 75 08 95 03 81 06 c0 c0
284 02 15 80 25 7F 75 08 95 01 81 06 C0 05 01 09 02
289 7F 75 08 95 01 81 06 C0 05 01 09 07 A1 01 85 05
292 C0 05 0C 09 01 A1 01 85 06 15 00 25 01 75 01 95
295 06 C0 05 0C 09 01 A1 01 85 03 09 05 15 00 26 FF
296 00 75 08 95 02 B1 02 C0
516 … 1 29 3 15 0 25 1 75 1 95 3 81 2 75 5 95 1 81 1 5 1 9 30 9 31 9 38 15 81 25 7f 75 8 95 3 81 6 c0 c0
/Documentation/devicetree/bindings/net/
Dqca,qca7000.txt54 local-mac-address = [ A0 B0 C0 D0 E0 F0 ];
84 local-mac-address = [ A0 B0 C0 D0 E0 F0 ];
/Documentation/devicetree/bindings/mfd/
Dbrcm,cru.yaml97 pinctrl@1c0 {
103 thermal@2c0 {
/Documentation/devicetree/bindings/reset/
Dbrcm,bcm63138-pmb.txt15 pmb0: reset-controller@4800c0 {
/Documentation/userspace-api/media/drivers/
Dccs.rst75 gain = m0 * x + c0 / (m1 * x + c1)
77 Either m0 or c0 will be zero. The constants that are device specific, can be
/Documentation/staging/
Dstatic-keys.rst234 ffffffff81044299: 65 48 8b 04 25 c0 b6 mov %gs:0xb6c0,%rax
244 ffffffff810442c7: 31 c0 xor %eax,%eax
254 ffffffff810441fa: 85 c0 test %eax,%eax
256 ffffffff810441fe: 65 48 8b 04 25 c0 b6 mov %gs:0xb6c0,%rax
266 ffffffff8104422c: 31 c0 xor %eax,%eax
/Documentation/networking/
Dtls-offload-reorder-bad.svg1c0 -12.5 114.47246 -25.007874 228.9449 -25.0c114.47241 0.007874016 228.94489 12.531496 228.94489 2…
Dtls-offload-reorder-good.svg1c0 -12.5 114.47246 -25.007874 228.9449 -25.0c114.47241 0.007874016 228.94489 12.531496 228.94489 2…
/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/
Dusb.txt23 usb@6c0 {
/Documentation/devicetree/bindings/phy/
Dbcm-ns-usb3-phy.yaml15 Known C0: BCM47094 rev 0
/Documentation/devicetree/bindings/display/
Dcirrus,clps711x-fb.txt20 fb: fb@800002c0 {
/Documentation/devicetree/bindings/pci/
Dnvidia,tegra194-pcie.yaml123 0: C0
132 0 : C0
159 1. If C0/C4/C5 run at x1/x2 link widths (irrespective of speed and MPS)
160 2. If C0/C1/C2/C3/C4/C5 operate at their respective max link widths and

123