Searched full:crypto (Results 1 – 25 of 1293) sorted by relevance
12345678910>>...52
/Linux-v5.10/Documentation/devicetree/bindings/crypto/ |
D | marvell-cesa.txt | 5 "marvell,orion-crypto" 6 "marvell,kirkwood-crypto" 7 "marvell,dove-crypto" 8 "marvell,armada-370-crypto" 9 "marvell,armada-xp-crypto" 10 "marvell,armada-375-crypto" 11 "marvell,armada-38x-crypto" 14 but this representation is deprecated and marvell,crypto-srams should 17 is deprecated and marvell,crypto-srams should be used instead 19 - clocks: reference to the crypto engines clocks. This property is not [all …]
|
D | allwinner,sun4i-a10-crypto.yaml | 4 $id: http://devicetree.org/schemas/crypto/allwinner,sun4i-a10-crypto.yaml# 16 - const: allwinner,sun4i-a10-crypto 18 - const: allwinner,sun5i-a13-crypto 19 - const: allwinner,sun4i-a10-crypto 21 - const: allwinner,sun6i-a31-crypto 22 - const: allwinner,sun4i-a10-crypto 24 - const: allwinner,sun7i-a20-crypto 25 - const: allwinner,sun4i-a10-crypto 26 - const: allwinner,sun8i-a33-crypto 28 - const: allwinner,sun8i-v3s-crypto [all …]
|
D | mv_cesa.txt | 5 "marvell,orion-crypto" 6 "marvell,kirkwood-crypto" 7 "marvell,dove-crypto" 10 but this representation is deprecated and marvell,crypto-srams should 13 is deprecated and marvell,crypto-srams should be used instead 15 - clocks: reference to the crypto engines clocks. This property is only 17 - marvell,crypto-srams: phandle to crypto SRAM definitions 20 - marvell,crypto-sram-size: SRAM size reserved for crypto operations, if not 25 crypto@30000 { 26 compatible = "marvell,orion-crypto"; [all …]
|
D | allwinner,sun8i-ce.yaml | 4 $id: http://devicetree.org/schemas/crypto/allwinner,sun8i-ce.yaml# 7 title: Allwinner Crypto Engine driver 15 - allwinner,sun8i-h3-crypto 16 - allwinner,sun8i-r40-crypto 17 - allwinner,sun50i-a64-crypto 18 - allwinner,sun50i-h5-crypto 19 - allwinner,sun50i-h6-crypto 50 const: allwinner,sun50i-h6-crypto 80 crypto: crypto@1c15000 { 81 compatible = "allwinner,sun8i-h3-crypto";
|
D | rockchip-crypto.txt | 4 - compatible: Should be "rockchip,rk3288-crypto" 8 - clocks: Reference to the clocks about crypto 11 "sclk" used to clock crypto accelerator 15 - reset-names: Must include the name "crypto-rst". 19 crypto: cypto-controller@ff8a0000 { 20 compatible = "rockchip,rk3288-crypto"; 27 reset-names = "crypto-rst";
|
/Linux-v5.10/drivers/crypto/caam/ |
D | compat.h | 14 #include <linux/crypto.h> 31 #include <crypto/algapi.h> 32 #include <crypto/null.h> 33 #include <crypto/aes.h> 34 #include <crypto/ctr.h> 35 #include <crypto/internal/des.h> 36 #include <crypto/gcm.h> 37 #include <crypto/sha.h> 38 #include <crypto/md5.h> 39 #include <crypto/chacha.h> [all …]
|
/Linux-v5.10/drivers/crypto/virtio/ |
D | virtio_crypto_mgr.c | 2 /* Management for virtio crypto devices (refer to adf_dev_mgr.c) 26 * @vcrypto_dev: Pointer to virtio crypto device. 28 * Function adds virtio crypto device to the global list. 29 * To be used by virtio crypto device specific drivers. 69 * @vcrypto_dev: Pointer to virtio crypto device. 71 * Function removes virtio crypto device from the acceleration framework. 72 * To be used by virtio crypto device specific drivers. 87 * Function returns the first virtio crypto device from the acceleration 90 * To be used by virtio crypto device specific drivers. 109 * @vcrypto_dev: Pointer to virtio crypto device. [all …]
|
/Linux-v5.10/drivers/crypto/ |
D | Kconfig | 4 bool "Hardware crypto devices" 7 Say Y here to get to see options for hardware crypto devices and 14 source "drivers/crypto/allwinner/Kconfig" 20 Some VIA processors come with an integrated crypto engine 74 + Crypto Express 2 up to 7 Coprocessor (CEXxC) 75 + Crypto Express 2 up to 7 Accelerator (CEXxA) 76 + Crypto Express 4 up to 7 EP11 Coprocessor (CEXxP) 88 and queues and some flags on crypto requests are interpreted as 104 down the use of the available crypto hardware. 270 tristate "Driver HIFN 795x crypto accelerator chips" [all …]
|
/Linux-v5.10/Documentation/ABI/testing/ |
D | debugfs-hisi-hpre | 3 Contact: linux-crypto@vger.kernel.org 9 Contact: linux-crypto@vger.kernel.org 16 Contact: linux-crypto@vger.kernel.org 25 Contact: linux-crypto@vger.kernel.org 32 Contact: linux-crypto@vger.kernel.org 38 Contact: linux-crypto@vger.kernel.org 45 Contact: linux-crypto@vger.kernel.org 52 Contact: linux-crypto@vger.kernel.org 61 Contact: linux-crypto@vger.kernel.org 68 Contact: linux-crypto@vger.kernel.org [all …]
|
D | debugfs-hisi-sec | 3 Contact: linux-crypto@vger.kernel.org 11 Contact: linux-crypto@vger.kernel.org 19 Contact: linux-crypto@vger.kernel.org 26 Contact: linux-crypto@vger.kernel.org 33 Contact: linux-crypto@vger.kernel.org 41 Contact: linux-crypto@vger.kernel.org 48 Contact: linux-crypto@vger.kernel.org 54 Contact: linux-crypto@vger.kernel.org 60 Contact: linux-crypto@vger.kernel.org 66 Contact: linux-crypto@vger.kernel.org [all …]
|
D | debugfs-hisi-zip | 3 Contact: linux-crypto@vger.kernel.org 9 Contact: linux-crypto@vger.kernel.org 15 Contact: linux-crypto@vger.kernel.org 24 Contact: linux-crypto@vger.kernel.org 31 Contact: linux-crypto@vger.kernel.org 38 Contact: linux-crypto@vger.kernel.org 45 Contact: linux-crypto@vger.kernel.org 54 Contact: linux-crypto@vger.kernel.org 61 Contact: linux-crypto@vger.kernel.org 67 Contact: linux-crypto@vger.kernel.org [all …]
|
/Linux-v5.10/drivers/crypto/ccp/ |
D | Makefile | 15 obj-$(CONFIG_CRYPTO_DEV_CCP_CRYPTO) += ccp-crypto.o 16 ccp-crypto-objs := ccp-crypto-main.o \ 17 ccp-crypto-aes.o \ 18 ccp-crypto-aes-cmac.o \ 19 ccp-crypto-aes-xts.o \ 20 ccp-crypto-aes-galois.o \ 21 ccp-crypto-des3.o \ 22 ccp-crypto-rsa.o \ 23 ccp-crypto-sha.o
|
/Linux-v5.10/Documentation/crypto/ |
D | architecture.rst | 1 Kernel Crypto API Architecture 7 The kernel crypto API provides different API calls for the following 23 The kernel crypto API provides implementations of single block ciphers 24 and message digests. In addition, the kernel crypto API provides 36 See /proc/crypto and search for "name". For example: 60 The kernel crypto API provides synchronous and asynchronous API 64 operation which is performed synchronously by the kernel crypto API. 66 Therefore, the kernel crypto API calls work like regular function calls. 68 conceptually similar to any other crypto library. 70 Asynchronous operation is provided by the kernel crypto API which [all …]
|
D | intro.rst | 1 Kernel Crypto API Interface Specification 7 The kernel crypto API offers a rich set of cryptographic ciphers as well 12 To understand and properly use the kernel crypto API a brief explanation 18 The kernel crypto API refers to all algorithms as "transformations". 20 cryptographic operations, the kernel crypto API also knows compression 23 The kernel crypto API serves the following entity types: 28 called by consumers using the kernel crypto API 30 This specification is intended for consumers of the kernel crypto API as 35 register with the kernel crypto API). 50 transformation objects is held by a crypto API consumer or another [all …]
|
D | api-skcipher.rst | 4 .. kernel-doc:: include/linux/crypto.h 7 .. kernel-doc:: include/linux/crypto.h 13 .. kernel-doc:: include/crypto/skcipher.h 16 .. kernel-doc:: include/crypto/skcipher.h 22 .. kernel-doc:: include/crypto/skcipher.h 25 .. kernel-doc:: include/crypto/skcipher.h 31 .. kernel-doc:: include/linux/crypto.h 34 .. kernel-doc:: include/linux/crypto.h
|
D | api-digest.rst | 4 .. kernel-doc:: include/crypto/hash.h 7 .. kernel-doc:: include/crypto/hash.h 13 .. kernel-doc:: include/crypto/hash.h 16 .. kernel-doc:: include/crypto/hash.h 22 .. kernel-doc:: include/crypto/hash.h 25 .. kernel-doc:: include/crypto/hash.h 31 .. kernel-doc:: include/crypto/hash.h 34 .. kernel-doc:: include/crypto/hash.h
|
D | api-kpp.rst | 4 .. kernel-doc:: include/crypto/kpp.h 10 .. kernel-doc:: include/crypto/kpp.h 13 .. kernel-doc:: include/crypto/kpp.h 19 .. kernel-doc:: include/crypto/kpp.h 25 .. kernel-doc:: include/crypto/ecdh.h 28 .. kernel-doc:: include/crypto/ecdh.h 34 .. kernel-doc:: include/crypto/dh.h 37 .. kernel-doc:: include/crypto/dh.h
|
/Linux-v5.10/drivers/net/ethernet/chelsio/inline_crypto/ |
D | Kconfig | 3 # Chelsio inline crypto configuration 7 bool "Chelsio Inline Crypto support" 11 Enable support for inline crypto. 12 Allows enable/disable from list of inline crypto drivers. 17 tristate "Chelsio Crypto Inline TLS Driver" 22 Support Chelsio Inline TLS with Chelsio crypto accelerator. 29 tristate "Chelsio IPSec XFRM Tx crypto offload" 34 Support Chelsio Inline IPsec with Chelsio crypto accelerator. 47 crypto accelerator. CONFIG_CHELSIO_TLS_DEVICE flag can be enabled
|
/Linux-v5.10/arch/arm64/crypto/ |
D | Kconfig | 21 tristate "SHA-1 digest algorithm (ARMv8 Crypto Extensions)" 27 tristate "SHA-224/SHA-256 digest algorithm (ARMv8 Crypto Extensions)" 33 tristate "SHA-384/SHA-512 digest algorithm (ARMv8 Crypto Extensions)" 39 tristate "SHA3 digest algorithm (ARMv8.2 Crypto Extensions)" 45 tristate "SM3 digest algorithm (ARMv8.2 Crypto Extensions)" 51 tristate "SM4 symmetric cipher (ARMv8.2 Crypto Extensions)" 57 tristate "GHASH/AES-GCM using ARMv8 Crypto Extensions" 73 tristate "AES core cipher using ARMv8 Crypto Extensions" 79 tristate "AES in CCM mode using ARMv8 Crypto Extensions" 87 tristate "AES in ECB/CBC/CTR/XTS modes using ARMv8 Crypto Extensions"
|
/Linux-v5.10/include/crypto/ |
D | engine.h | 3 * Crypto engine API 10 #include <linux/crypto.h> 14 #include <crypto/algapi.h> 15 #include <crypto/aead.h> 16 #include <crypto/akcipher.h> 17 #include <crypto/hash.h> 18 #include <crypto/skcipher.h> 22 * struct crypto_engine - crypto hardware engine 29 * crypto-engine, in head position to keep order 30 * @list: link with the global crypto engine list [all …]
|
D | hash_info.h | 11 #include <crypto/sha.h> 12 #include <crypto/md5.h> 13 #include <crypto/streebog.h> 17 /* not defined in include/crypto/ */ 23 /* not defined in include/crypto/ */ 28 /* not defined in include/crypto/ */ 33 /* not defined in include/crypto/ */
|
/Linux-v5.10/Documentation/block/ |
D | inline-encryption.rst | 27 To allow for testing, we also want a crypto API fallback when actual 30 of the underlying devices if present, or else fall back to crypto API 84 blk-mq changes, other block layer changes and blk-crypto-fallback 88 struct request. These will be referred to as the ``crypto fields`` 93 We introduce ``block/blk-crypto-fallback.c``, which allows upper layers to remain 97 en/decrypt the bio with the blk-crypto-fallback. 102 concerned). ``blk-crypto-fallback`` sets the bounce bio's ``bi_end_io`` to an 106 is saved and overwritten by ``blk-crypto-fallback`` to 114 blk-crypto-fallback is used, the ciphertext written to disk (and hence the 120 ``blk-crypto-fallback``. We will eventually reach a point in blk-mq when a [all …]
|
/Linux-v5.10/drivers/staging/rtl8192e/ |
D | Kconfig | 15 tristate "Support for rtllib CCMP crypto" 17 select CRYPTO 22 CCMP crypto driver for rtllib. 27 tristate "Support for rtllib TKIP crypto" 33 TKIP crypto driver for rtllib. 38 tristate "Support for rtllib WEP crypto" 43 TKIP crypto driver for rtllib.
|
/Linux-v5.10/drivers/crypto/allwinner/ |
D | Kconfig | 6 Say Y here to get to see options for Allwinner hardware crypto devices 19 Some Allwinner SoC have a crypto accelerator named 36 tristate "Support for Allwinner Crypto Engine cryptographic offloader" 46 Select y here to have support for the crypto Engine availlable on 48 The Crypto Engine handle AES/3DES ciphers in ECB/CBC mode. 73 bool "Support for Allwinner Crypto Engine PRNG" 78 the Pseudo-Random Number Generator found in the Crypto Engine. 81 bool "Support for Allwinner Crypto Engine TRNG" 86 the True Random Number Generator found in the Crypto Engine.
|
/Linux-v5.10/block/ |
D | blk-crypto-fallback.c | 10 #define pr_fmt(fmt) "blk-crypto-fallback: " fmt 12 #include <crypto/skcipher.h> 14 #include <linux/blk-crypto.h> 16 #include <linux/crypto.h> 22 #include "blk-crypto-internal.h" 27 "Number of preallocated bounce pages for the blk-crypto crypto API fallback"); 32 "Number of keyslots for the blk-crypto crypto API fallback"); 37 …"Number of preallocated bio fallback crypto contexts for blk-crypto to use during crypto API fallb… 64 * Allocating a crypto tfm during I/O can deadlock, so we have to preallocate 137 * The crypto API fallback KSM ops - only used for a bio when it specifies a [all …]
|
12345678910>>...52