Searched refs:J (Results 1 – 8 of 8) sorted by relevance
| /optee_os/core/arch/arm/dts/ |
| H A D | stm32mp15-pinctrl.dtsi | 728 <STM32_PINMUX('J', 0, AF14)>, /* LCD_R1 */ 729 <STM32_PINMUX('J', 1, AF14)>, /* LCD_R2 */ 730 <STM32_PINMUX('J', 2, AF14)>, /* LCD_R3 */ 731 <STM32_PINMUX('J', 3, AF14)>, /* LCD_R4 */ 732 <STM32_PINMUX('J', 4, AF14)>, /* LCD_R5 */ 733 <STM32_PINMUX('J', 5, AF14)>, /* LCD_R6 */ 734 <STM32_PINMUX('J', 6, AF14)>, /* LCD_R7 */ 735 <STM32_PINMUX('J', 7, AF14)>, /* LCD_G0 */ 736 <STM32_PINMUX('J', 8, AF14)>, /* LCD_G1 */ 737 <STM32_PINMUX('J', 9, AF14)>, /* LCD_G2 */ [all …]
|
| H A D | stm32mp15xx-dhcor-avenger96.dtsi | 176 "", "AV96-J", "", "",
|
| H A D | stm32mp15xx-dhcom-som.dtsi | 248 "DHCOM-J", "DHCOM-W", "DHCOM-V", "DHCOM-U",
|
| /optee_os/core/arch/arm/crypto/ |
| H A D | ghash-ce-core_a32.S | 100 vmull.p8 t2q, t2l, \bd @ J = A3*B 111 veor t2q, t2q, t4q @ N = I + J
|
| /optee_os/core/lib/libtomcrypt/src/hashes/ |
| H A D | rmd160.c | 41 #define J(x, y, z) ((x) ^ ((y) | ~(z))) macro 65 (a) += J((b), (c), (d)) + (x) + 0xa953fd4eUL;\ 90 (a) += J((b), (c), (d)) + (x) + 0x50a28be6UL;\
|
| H A D | rmd320.c | 36 #define J(x, y, z) ((x) ^ ((y) | ~(z))) macro 60 (a) += J((b), (c), (d)) + (x) + 0xa953fd4eUL;\ 85 (a) += J((b), (c), (d)) + (x) + 0x50a28be6UL;\
|
| /optee_os/ |
| H A D | MAINTAINERS | 232 R: Vesa Jääskeläinen <vesa.jaaskelainen@vaisala.com> [@vesajaaskelainen]
|
| /optee_os/lib/libmbedtls/mbedtls/ |
| H A D | ChangeLog | 680 of ECDSA and/or EC J-PAKE when those are provided by a driver. However, 733 * When all of ECDH, ECDSA and EC J-PAKE are either disabled or provided by 879 * Fix the J-PAKE driver interface for user and peer to accept any values 1038 * Add a driver dispatch layer for EC J-PAKE, enabling alternative 1039 implementations of EC J-PAKE through the driver entry points. 1047 * When a PSA driver for EC J-PAKE is present, it is now possible to disable 1134 * Allow setting user and peer identifiers for EC J-PAKE operation 1217 * Expose the EC J-PAKE functionality through the Draft PSA PAKE Crypto API. 1222 - RSA OAEP and PSS (PKCS#1 v2.1), PKCS5, PKCS12 and EC J-PAKE now use 1269 * The TLS 1.2 EC J-PAKE key exchange can now use the PSA Crypto API. [all …]
|