/Linux-v6.6/arch/arm/crypto/ |
D | poly1305-armv4.pl | 496 my ($D0,$D1,$D2,$D3,$D4, $H0,$H1,$H2,$H3,$H4) = map("q$_",(5..14)); 800 vld4.32 {$H0#lo[0],$H1#lo[0],$H2#lo[0],$H3#lo[0]},[$inp]! 808 vrev32.8 $H1,$H1 819 vsri.u32 $H2#lo,$H1#lo,#20 820 vshl.u32 $H1#lo,$H1#lo,#6 823 vsri.u32 $H1#lo,$H0#lo,#26 827 vbic.i32 $H1#lo,#0xfc000000 831 vadd.i32 $H1#hi,$H1#lo,$D1#lo 846 vld4.32 {$H0#lo,$H1#lo,$H2#lo,$H3#lo},[$inp] @ inp[0:1] 848 vld4.32 {$H0#hi,$H1#hi,$H2#hi,$H3#hi},[$in2] @ inp[2:3] (or 0) [all …]
|
/Linux-v6.6/arch/x86/crypto/ |
D | poly1305-x86_64-cryptogams.pl | 419 my ($H0,$H1,$H2,$H3,$H4, $T0,$T1,$T2,$T3,$T4, $D0,$D1,$D2,$D3,$D4, $MASK) = 713 vmovd %rdx#d,$H1 815 vmovd %rdx#d,$H1 845 vmovd 4*1($ctx),$H1 989 vmovdqa $H1,0x10(%r11) # 990 vpmuludq $T3,$H2,$H1 # h3*r1 992 vpaddq $H1,$D4,$D4 # d4 += h3*r1 995 vpmuludq $T1,$H2,$H1 # h1*r1 998 vpaddq $H1,$D2,$D2 # d2 += h1*r1 1006 vpmuludq $T1,$H3,$H1 # h1*r2 [all …]
|
/Linux-v6.6/arch/arm64/crypto/ |
D | poly1305-armv8.pl | 266 my ($H0,$H1,$H2,$H3,$H4) = map("v$_.2s",(24..28)); 436 fmov ${H1},x11 466 fmov ${H1},x11 650 add $IN01_1,$IN01_1,$H1 716 xtn $H1,$ACC1 725 bic $H1,#0xfc,lsl#24 734 add $H1,$H1,$T0.2s // h0 -> h1 752 add $IN23_1,$IN01_1,$H1 802 add $IN01_1,$IN01_1,$H1
|
/Linux-v6.6/Documentation/devicetree/bindings/security/tpm/ |
D | google,cr50.txt | 1 * H1 Secure Microcontroller with Cr50 Firmware on SPI Bus. 3 H1 Secure Microcontroller running Cr50 firmware provides several
|
/Linux-v6.6/drivers/gpu/drm/i915/ |
D | intel_step.h | 56 func(H1) \
|
/Linux-v6.6/arch/arm64/boot/dts/qcom/ |
D | sc7280-idp-ec-h1.dtsi | 3 * sc7280 EC/H1 over SPI (common between IDP2 and CRD)
|
/Linux-v6.6/Documentation/ABI/testing/ |
D | debugfs-wilco-ec | 6 tests, we need to ensure that the H1 chip is properly setting
|
/Linux-v6.6/arch/mips/boot/dts/pic32/ |
D | pic32mzda_sk.dts | 104 pins = "H0", "H1", "H2";
|
/Linux-v6.6/arch/arm/boot/dts/renesas/ |
D | r8a7779-marzen.dts | 3 * Device Tree Source for the R-Car H1 (R8A77790) Marzen board
|
D | r8a7779.dtsi | 3 * Device Tree Source for the R-Car H1 (R8A77790) SoC
|
/Linux-v6.6/drivers/iio/pressure/ |
D | bmp280.h | 339 u8 H1; member
|
D | bmp280-core.c | 242 calib->H1 = tmp; in bme280_read_calib() 302 var -= ((((var >> 15) * (var >> 15)) >> 7) * (s32)calib->H1) >> 4; in bmp280_compensate_humidity()
|
/Linux-v6.6/drivers/soc/renesas/ |
D | Kconfig | 73 bool "ARM32 Platform support for R-Car H1" 375 bool "System Controller support for R-Car H1" if COMPILE_TEST
|
/Linux-v6.6/drivers/clk/renesas/ |
D | Kconfig | 104 bool "R-Car H1 clock support" if COMPILE_TEST
|
/Linux-v6.6/drivers/pinctrl/renesas/ |
D | Kconfig | 98 bool "pin control support for R-Car H1" if COMPILE_TEST
|
/Linux-v6.6/drivers/char/tpm/ |
D | Kconfig | 74 If you have a H1 secure module running Cr50 firmware on SPI bus,
|
/Linux-v6.6/drivers/pinctrl/aspeed/ |
D | pinctrl-aspeed-g4.c | 1104 #define H1 135 macro 1105 SIG_EXPR_LIST_DECL_SINGLE(H1, USB11HDN3, USB11H3, USB11H3_DESC); 1106 PIN_DECL_1(H1, GPIOQ7, USB11HDN3); 2030 ASPEED_PINCTRL_PIN(H1),
|
/Linux-v6.6/Documentation/driver-api/ |
D | pin-control.rst | 71 PINCTRL_PIN(63, "H1"), 444 On the bottom row at { A1, B1, C1, D1, E1, F1, G1, H1 } we have something
|
/Linux-v6.6/arch/arm/ |
D | Kconfig.debug | 945 via SCIF2 on Renesas R-Car H1 (R8A7779).
|