/kernel/linux/linux-5.10/arch/arm/crypto/ |
D | poly1305-armv4.pl | 496 my ($D0,$D1,$D2,$D3,$D4, $H0,$H1,$H2,$H3,$H4) = map("q$_",(5..14)); 557 vmull.u32 $D3,$R3,${R0}[1] 563 vmlal.u32 $D3,$R2,${R1}[1] 568 vmlal.u32 $D3,$R1,${R2}[1] 573 vmlal.u32 $D3,$R0,${R3}[1] 578 vmlal.u32 $D3,$R4,${S4}[1] 633 vshr.u64 $T0,$D3,#26 634 vmovn.i64 $D3#lo,$D3 638 vbic.i32 $D3#lo,#0xfc000000 @ &=0x03ffffff 655 vadd.i32 $D3#lo,$D3#lo,$T1#lo @ h2 -> h3 [all …]
|
/kernel/linux/linux-5.10/arch/x86/crypto/ |
D | poly1305-x86_64-cryptogams.pl | 420 my ($H0,$H1,$H2,$H3,$H4, $T0,$T1,$T2,$T3,$T4, $D0,$D1,$D2,$D3,$D4, $MASK) = 912 vpshufd \$0xEE,$D4,$D3 # 34xx -> 3434 914 vmovdqa $D3,-0x90(%r11) 921 vpshufd \$0xEE,$D2,$D3 924 vmovdqa $D3,-0x70(%r11) 931 vpshufd \$0xEE,$D1,$D3 934 vmovdqa $D3,-0x50(%r11) 941 vpshufd \$0xEE,$D0,$D3 944 vmovdqa $D3,-0x30(%r11) 950 vpshufd \$0xEE,$D2,$D3 [all …]
|
/kernel/linux/linux-5.10/Documentation/i2c/ |
D | i2c-topology.rst | 135 '--| dev D3 | 153 of the entire operation. But accesses to D3 are possibly interleaved 195 '--| dev D3 | 216 This means that accesses to both D2 and D3 are locked out for the full 234 '--| dev D4 | '--| dev D3 | 258 '--| dev D4 | '--| dev D3 | 263 are locked). But accesses to D3 and D4 are possibly interleaved at 264 any point. Accesses to D3 locks out D1 and D2, but accesses to D4 279 '--| dev D4 | '--| dev D3 | 282 When device D1 is accessed, accesses to D2 and D3 are locked out [all …]
|
/kernel/linux/linux-5.10/arch/arm64/boot/dts/amlogic/ |
D | meson-gxbb-nanopi-k2.dts | 210 "Eth RX D3", "Eth RGMII TX Clk", "Eth TX En", 211 "Eth TX D0", "Eth TX D1", "Eth TX D2", "Eth TX D3", 217 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3", "eMMC D4", 224 "SDCard D3", "SDCard D2", "SDCard Det", 242 "WIFI SDIO D3", "WIFI SDIO CLK", "WIFI SDIO CMD",
|
D | meson-gxl-s905x-khadas-vim.dts | 144 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3", 150 "SDCard D3", "SDCard D2", "SDCard Det", 158 "WIFI SDIO D3", "WIFI SDIO CLK", "WIFI SDIO CMD",
|
D | meson-gxbb-odroidc2.dts | 268 "Eth RX D3", "Eth RGMII TX Clk", "Eth TX En", 269 "Eth TX D0", "Eth TX D1", "Eth TX D2", "Eth TX D3", 274 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3", "eMMC D4", 280 "SDCard D3", "SDCard D2", "SDCard Det",
|
D | meson-gxl-s905x-libretech-cc.dts | 269 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3", 275 "SDCard D3", "SDCard D2", "SDCard Det",
|
D | meson-gxl-s805x-libretech-ac.dts | 246 "eMMC D0", "eMMC D1", "eMMC D2", "eMMC D3",
|
/kernel/linux/linux-5.10/arch/arm/boot/dts/ |
D | stm32f7-pinctrl.dtsi | 231 <STM32_PINMUX('C', 11, AF12)>, /* SDMMC1 D3 */ 244 <STM32_PINMUX('C', 11, AF12)>, /* SDMMC1 D3 */ 262 <STM32_PINMUX('B', 4, AF10)>, /* SDMMC2 D3 */ 275 <STM32_PINMUX('B', 4, AF10)>, /* SDMMC2 D3 */
|
D | efm32gg-dk3750.dts | 61 cs-gpios = <&gpio 51 1>; // D3
|
D | r8a7792-wheat.dts | 34 regulator-name = "D3.3V";
|
D | r8a7792-blanche.dts | 35 regulator-name = "D3.3V";
|
/kernel/linux/linux-5.10/arch/m68k/fpsp040/ |
D | srem_mod.S | 117 movel 8(%a0),%d5 | ...(D3,D4,D5) is |Y| 133 subl %d6,%d3 | ...(D3,D4,D5) is normalized 147 orl %d7,%d4 | ...(D3,D4,D5) normalized 152 addil #0x00003FFE,%d3 | ...(D3,D4,D5) normalized 207 clrl %d3 | ...D3 is Q
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
D | efm32-spi.txt | 29 cs-gpios = <&gpio 51 1>; // D3
|
/kernel/linux/linux-5.10/drivers/soc/renesas/ |
D | Kconfig | 184 bool "ARM64 Platform support for R-Car D3" 188 This enables support for the Renesas R-Car D3 SoC. 291 bool "System Controller support for R-Car D3" if COMPILE_TEST
|
/kernel/linux/linux-5.10/Documentation/networking/ |
D | plip.rst | 145 D3->ACK 5 - 10 10 - 5 176 D3->D3 5 - 5
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
D | renesas,du.txt | 28 - "renesas,du-r8a77995" for R8A77995 (R-Car D3) compatible DU 96 R8A77995 (R-Car D3) DPAD 0 LVDS 0 LVDS 1 -
|
/kernel/linux/linux-5.10/Documentation/spi/ |
D | spi-lm70llp.rst | 42 D3 5 --> V+ 5
|
D | butterfly.rst | 67 SCK J403.PE4/USCK pin 5/D3
|
/kernel/linux/linux-5.10/Documentation/power/ |
D | pci.rst | 85 The PCI PM Spec defines 4 operating states for devices (D0-D3) and for buses 90 There are two variants of the D3 state defined by the specification. The first 91 one is D3hot, referred to as the software accessible D3, because devices can be 118 | D0 | D1, D2, D3 | 120 | D1 | D2, D3 | 122 | D2 | D3 | 124 | D1, D2, D3 | D0 | 133 while in any power state (D0-D3), but they are not required to be capable 166 labeled as D0, D1, D2, and D3 that roughly correspond to the native PCI PM 167 D0-D3 states (although the difference between D3hot and D3cold is not taken [all …]
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/can/ |
D | rcar_canfd.txt | 17 - "renesas,r8a77995-canfd" for R8A77995 (R-Car D3) compatible controller.
|
/kernel/linux/linux-5.10/drivers/clk/renesas/ |
D | Kconfig | 146 bool "R-Car D3 clock support" if COMPILE_TEST
|
/kernel/linux/linux-5.10/Documentation/driver-api/iio/ |
D | buffers.rst | 55 |D3 |D2 |D1 |D0 | X | X | X | X | (LOW byte, address 0x06)
|
/kernel/linux/linux-5.10/arch/arm64/boot/dts/renesas/ |
D | r8a77980-condor.dts | 36 regulator-name = "D3.3V";
|
/kernel/linux/linux-5.10/drivers/pinctrl/aspeed/ |
D | pinctrl-aspeed-g6.c | 1389 #define D3 223 macro 1390 SIG_EXPR_LIST_DECL_SESG(D3, RGMII2TXD1, RGMII2, SIG_DESC_SET(SCU400, 15), 1392 SIG_EXPR_LIST_DECL_SESG(D3, RMII2TXD1, RMII2, SIG_DESC_SET(SCU400, 15), 1394 PIN_DECL_2(D3, GPIO18B7, RGMII2TXD1, RMII2TXD1); 1446 FUNC_GROUP_DECL(RGMII2, D4, C2, C1, D3, E4, F5, D2, E3, D1, F4, E2, E1); 1447 FUNC_GROUP_DECL(RMII2, D4, C2, C1, D3, D2, D1, F4, E2, E1); 1790 ASPEED_PINCTRL_PIN(D3), 2606 ASPEED_SB_PINCONF(PIN_CONFIG_BIAS_PULL_DOWN, B2, D3, SCU40C, 1), 2607 ASPEED_SB_PINCONF(PIN_CONFIG_BIAS_DISABLE, B2, D3, SCU40C, 1),
|