Home
last modified time | relevance | path

Searched refs:H4 (Results 1 – 14 of 14) sorted by relevance

/linux/arch/x86/crypto/
H A Dpoly1305-x86_64-cryptogams.pl419 my ($H0,$H1,$H2,$H3,$H4, $T0,$T1,$T2,$T3,$T4, $D0,$D1,$D2,$D3,$D4, $MASK) =
716 vmovd $h2#d,$H4
818 vmovd $h2#d,$H4
848 vmovd 4*4($ctx),$H4
999 vmovdqa $H4,0x40(%r11) #
1004 vmovdqa 0x40(%rsp),$H4 # s2^2
1011 vpmuludq $T4,$H4,$H0 # h4*s2
1012 vpmuludq $T3,$H4,$H4 # h3*s2
1015 vpaddq $H4,$D0,$D0 # d0 += h3*s2
1017 vmovdqa 0x80(%rsp),$H4 # s4^2
[all …]
/linux/arch/arm/crypto/
H A Dpoly1305-armv4.pl496 my ($D0,$D1,$D2,$D3,$D4, $H0,$H1,$H2,$H3,$H4) = map("q$_",(5..14));
619 @ 5*H4 - by 5*5 52-bit addends, or 57 bits. But when hashing the
621 @ 5*H4 by 5*5*3, or 59[!] bits. How is this relevant? vmlal.u32
627 @ one has to watch for H2 (which is narrower than H0) and 5*H4
801 vmov.32 $H4#lo[0],$padbit
811 vsri.u32 $H4#lo,$H3#lo,#8 @ base 2^32 -> base 2^26
816 vadd.i32 $H4#hi,$H4#lo,$D4#lo @ add hash value and move to #hi
845 vmov.i32 $H4,#1<<24 @ padbit, yes, always
860 vsri.u32 $H4,$H3,#8 @ base 2^32 -> base 2^26
916 vadd.i32 $H4#lo,$H4#lo,$D4#lo
[all …]
/linux/arch/arm64/crypto/
H A Dpoly1305-armv8.pl266 my ($H0,$H1,$H2,$H3,$H4) = map("v$_.2s",(24..28));
439 fmov ${H4},x14
469 fmov ${H4},x14
675 add $IN01_4,$IN01_4,$H4
715 xtn $H4,$ACC4
718 bic $H4,#0xfc,lsl#24
736 add $H4,$H4,$T1.2s // h3 -> h4
754 add $IN23_4,$IN01_4,$H4
817 add $IN01_4,$IN01_4,$H4
/linux/arch/powerpc/crypto/
H A Daes-gcm-p10.S15 # (X1.h * H4.h + xX.l * H4.l + X1 * H4) +
238 vpmsumd 23, 12, 15 # H4.L * X.L
247 vpmsumd 24, 13, 15 # H4.L * X.H + H4.H * X.L
267 vpmsumd 24, 14, 15 # H4.H * X.H
296 vpmsumd 23, 12, 15 # H4.L * X.L
305 vpmsumd 24, 13, 15 # H4.L * X.H + H4.H * X.L
326 vpmsumd 24, 14, 15 # H4.H * X.H
348 vpmsumd 23, 12, 19 # H4.L * X.L
354 vpmsumd 24, 13, 19 # H4.L * X.H + H4.H * X.L
375 vpmsumd 24, 14, 19 # H4.H * X.H
/linux/Documentation/devicetree/bindings/net/bluetooth/
H A Dnokia,h4p-bluetooth.txt5 vendors and modified device API. Those devices speak a protocol named H4+
6 (also known as h4p) by Nokia, which is similar to the H4 protocol from the
7 Bluetooth standard. In addition to the H4 protocol it specifies two more
/linux/drivers/bluetooth/
H A DKconfig126 bool "UART (H4) protocol support"
129 UART (H4) is serial protocol for communication between Bluetooth
133 Say Y here to compile support for HCI UART (H4) protocol.
136 tristate "UART Nokia H4+ protocol support"
144 Nokia H4+ is serial protocol for communication between Bluetooth
148 Say Y here to compile support for Nokia's H4+ protocol.
248 over serial port interface(H4) between controller and host.
/linux/arch/arm/boot/dts/ti/omap/
H A Domap2420-h4.dts10 model = "TI OMAP2420 H4 board";
/linux/arch/arm64/boot/dts/amlogic/
H A Dmeson-a1-ad402.dts133 /* Bluetooth HCI H4 */
/linux/drivers/pinctrl/aspeed/
H A Dpinctrl-aspeed-g5.c1405 #define H4 191 macro
1406 SIG_EXPR_LIST_DECL_SINGLE(H4, GPIOX7, GPIOX7, SIG_DESC_SET(SCUA4, 7));
1407 SIG_EXPR_LIST_DECL_SINGLE(H4, ADC15, ADC15);
1408 PIN_DECL_(H4, SIG_EXPR_LIST_PTR(H4, GPIOX7), SIG_EXPR_LIST_PTR(H4, ADC15));
1409 FUNC_GROUP_DECL(ADC15, H4);
2040 ASPEED_PINCTRL_PIN(H4),
2595 ASPEED_SB_PINCONF(PIN_CONFIG_BIAS_PULL_DOWN, H4, H4, SCUA8, 19),
2596 ASPEED_SB_PINCONF(PIN_CONFIG_BIAS_DISABLE, H4, H4, SCUA8, 19),
H A Dpinctrl-aspeed-g4.c1080 #define H4 132 macro
1081 SIG_EXPR_LIST_DECL_SINGLE(H4, SCL14, I2C14, I2C14_DESC);
1082 PIN_DECL_1(H4, GPIOQ4, SCL14);
1088 FUNC_GROUP_DECL(I2C14, H4, H3);
2036 ASPEED_PINCTRL_PIN(H4),
/linux/drivers/iio/pressure/
H A Dbmp280.h356 s16 H4; member
H A Dbmp280-core.c391 calib->H4 = sign_extend32(((be16_to_cpu(data->be16) >> 4) & 0xff0) | in bme280_read_calib()
447 var = (((((s32)adc_humidity << 14) - (calib->H4 << 20) - (calib->H5 * var)) in bme280_compensate_humidity()
/linux/drivers/iio/chemical/
H A Dbme680_core.c50 H4 = 4, enumerator
207 calib->par_h4 = data->bme680_cal_buf_2[H4]; in bme680_read_calib()
/linux/arch/arm/boot/dts/aspeed/
H A Daspeed-bmc-facebook-harma.dts689 /*H4-H7 line 120-127*/