| /Linux-v5.10/drivers/scsi/aic7xxx/ |
| D | aic7xxx_seq.h_shipped | 194 0x01, 0x64, 0xd8, 0x31,
195 0x01, 0x64, 0x32, 0x31,
196 0x5b, 0x64, 0xc8, 0x28,
197 0x30, 0x64, 0xca, 0x18,
199 0xff, 0x64, 0x8e, 0x79,
202 0x01, 0x64, 0x86, 0x61,
206 0xff, 0x64, 0xc8, 0x18,
207 0xff, 0x64, 0x80, 0x69,
241 0xbf, 0x64, 0x58, 0x7a,
242 0x80, 0x64, 0xa0, 0x73,
[all …]
|
| /Linux-v5.10/arch/x86/include/asm/ |
| D | syscall_wrapper.h | 93 __SYS_STUB0(x64, sys_##name)
96 __SYS_STUBx(x64, sys##name, \
100 __COND_SYSCALL(x64, sys_##name)
103 __SYS_NI(x64, sys_##name)
|
| /Linux-v5.10/Documentation/devicetree/bindings/media/ |
| D | renesas,drif.txt | 100 reg = <0 0xe6f40000 0 0x64>;
121 reg = <0 0xe6f50000 0 0x64>;
148 reg = <0 0xe6f40000 0 0x64>;
161 reg = <0 0xe6f50000 0 0x64>;
|
| D | stih-cec.txt | 18 reg = <0x94a087c 0x64>;
|
| /Linux-v5.10/Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 50 0x64,
61 0x64
69 0x64 brightness value) inclusive. Each of those index values is regarded
|
| /Linux-v5.10/Documentation/devicetree/bindings/net/ |
| D | marvell-bt-8xxx.txt | 64 marvell,wakeup-gap-ms = /bits/ 16 <0x64>;
81 marvell,wakeup-gap-ms = /bits/ 16 <0x64>;
|
| /Linux-v5.10/lib/crypto/ |
| D | curve25519-fiat32.c | 138 { u32 x64; u8/*bool*/ x65 = addcarryx_u25(x61, x29, x62, &x64); in fe_freeze() local
154 out[3] = x64; in fe_freeze()
358 { u64 x64 = (x63 + x57); in fe_mul_impl() local
400 { u64 x106 = (x104 + x64); in fe_mul_impl()
501 { u64 x64 = (x63 + x29); in fe_sqr_impl() local
502 { u64 x65 = (x64 >> 0x1a); in fe_sqr_impl()
503 { u32 x66 = ((u32)x64 & 0x3ffffff); in fe_sqr_impl()
681 { u64 x64 = (x63 + x57); in fe_mul_121666_impl() local
723 { u64 x106 = (x104 + x64); in fe_mul_121666_impl()
|
| /Linux-v5.10/arch/c6x/lib/ |
| D | mpyll.S | 10 ;; 64x64 multiply
|
| /Linux-v5.10/arch/mips/boot/dts/loongson/ |
| D | loongson64g-package.dtsi | 26 reg = <0 0x3ff01400 0x64>;
|
| D | loongson64c-package.dtsi | 29 reg = <0 0x3ff01400 0x64>;
|
| D | loongson64v_4core_virtio.dts | 28 reg = <0 0x3ff01400 0x64>;
|
| /Linux-v5.10/Documentation/bpf/ |
| D | bpf_design_QA.rst | 18 Q: Is BPF a generic instruction set similar to x64 and arm64?
34 with two most used architectures x64 and arm64 (and takes into
47 (unlike x64 ISA that allows msft, cdecl and other conventions)
137 Q: Why BPF_DIV instruction doesn't map to x64 div?
139 A: Because if we picked one-to-one relationship to x64 it would have made
|
| /Linux-v5.10/Documentation/i2c/ |
| D | slave-eeprom-backend.rst | 16 24c02, read/write, address 0x64:
|
| /Linux-v5.10/Documentation/devicetree/bindings/phy/ |
| D | ti-phy.txt | 74 <0x4a084800 0x64>,
90 <0x4A096400 0x64>, /* phy_tx */
|
| /Linux-v5.10/Documentation/trace/ |
| D | uprobetracer.rst | 54 (x8/x16/x32/x64), "string" and bitfield are supported.
67 or 'x64' is used depends on the architecture (e.g. x86-32 uses x32, and
68 x86-64 uses x64).
|
| /Linux-v5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-lm3601x.txt | 37 reg = <0x64>;
|
| D | leds-is31fl319x.txt | 13 - reg: 0x64, 0x65, 0x66, or 0x67.
|
| /Linux-v5.10/Documentation/devicetree/bindings/power/supply/ |
| D | ltc2941.txt | 25 reg = <0x64>;
|
| /Linux-v5.10/arch/arm/boot/dts/ |
| D | aspeed-bmc-opp-zaius.dts | 221 reg = <0x64>;
349 reg = <0x64>;
408 reg = <0x64>;
|
| D | lpc32xx.dtsi | 126 pnx,timeout = <0x64>;
289 pnx,timeout = <0x64>;
300 pnx,timeout = <0x64>;
|
| D | imx27-phytec-phycard-s-rdk.dts | 70 reg = <0x64>;
|
| D | imx6qdl-phytec-pbab01.dtsi | 137 reg = <0x64>;
|
| D | spear320.dtsi | 134 st-plgpio,ie-reg = <0x64>;
|
| /Linux-v5.10/Documentation/devicetree/bindings/clock/ |
| D | ti,cdce925.txt | 42 reg = <0x64>;
|
| /Linux-v5.10/Documentation/usb/ |
| D | linux.inf | 23 ; Decoration for x64 architecture
|
