Home
last modified time | relevance | path

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

/kernel/linux/linux-5.10/arch/arm/crypto/
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 …]
Dpoly1305-core.S_shipped525 @ H0>>+H1>>+H2>>+H3>>+H4
526 @ H3>>+H4>>*5+H0>>+H1
539 @ H0, H2, H3 are guaranteed to be 26 bits wide, while H1 and H4
546 @ H4 = H4*R0 + H3*R1 + H2*R2 + H1*R3 + H0 * R4,
556 @ 5*H4 - by 5*5 52-bit addends, or 57 bits. But when hashing the
558 @ 5*H4 by 5*5*3, or 59[!] bits. How is this relevant? vmlal.u32
564 @ one has to watch for H2 (which is narrower than H0) and 5*H4
/kernel/linux/linux-5.10/arch/x86/crypto/
Dpoly1305-x86_64-cryptogams.pl420 my ($H0,$H1,$H2,$H3,$H4, $T0,$T1,$T2,$T3,$T4, $D0,$D1,$D2,$D3,$D4, $MASK) =
717 vmovd $h2#d,$H4
819 vmovd $h2#d,$H4
849 vmovd 4*4($ctx),$H4
1000 vmovdqa $H4,0x40(%r11) #
1005 vmovdqa 0x40(%rsp),$H4 # s2^2
1012 vpmuludq $T4,$H4,$H0 # h4*s2
1013 vpmuludq $T3,$H4,$H4 # h3*s2
1016 vpaddq $H4,$D0,$D0 # d0 += h3*s2
1018 vmovdqa 0x80(%rsp),$H4 # s4^2
[all …]
/kernel/linux/linux-5.10/arch/arm64/crypto/
Dpoly1305-armv8.pl266 my ($H0,$H1,$H2,$H3,$H4) = map("v$_.2s",(24..28));
439 fmov ${H4},x14
469 fmov ${H4},x14
674 add $IN01_4,$IN01_4,$H4
714 xtn $H4,$ACC4
717 bic $H4,#0xfc,lsl#24
735 add $H4,$H4,$T1.2s // h3 -> h4
753 add $IN23_4,$IN01_4,$H4
816 add $IN01_4,$IN01_4,$H4
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dnokia-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
/kernel/linux/linux-5.10/drivers/bluetooth/
DKconfig109 bool "UART (H4) protocol support"
112 UART (H4) is serial protocol for communication between Bluetooth
116 Say Y here to compile support for HCI UART (H4) protocol.
119 tristate "UART Nokia H4+ protocol support"
127 Nokia H4+ is serial protocol for communication between Bluetooth
131 Say Y here to compile support for Nokia's H4+ protocol.
231 over serial port interface(H4) between controller and host.
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Domap2420-h4.dts10 model = "TI OMAP2420 H4 board";
/kernel/linux/linux-5.10/drivers/iio/pressure/
Dbmp280-core.c72 s16 H4; member
236 calib->H4 = sign_extend32(((be16_to_cpu(b16) >> 4) & 0xff0) | in bmp280_read_calib()
268 var = ((((adc_humidity << 14) - (calib->H4 << 20) - (calib->H5 * var)) in bmp280_compensate_humidity()
/kernel/linux/linux-5.10/drivers/pinctrl/aspeed/
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),
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),
/kernel/linux/linux-5.10/drivers/usb/phy/
DKconfig41 products including H2, H3, and H4 development boards for Texas