Home
last modified time | relevance | path

Searched full:crypto (Results 1 – 25 of 1120) sorted by relevance

12345678910>>...45

/linux/tools/perf/pmu-events/arch/s390/cf_z16/
H A Dpai_crypto.json3 "Unit": "PAI-CRYPTO",
6 "BriefDescription": "CRYPTO ALL",
10 "Unit": "PAI-CRYPTO",
17 "Unit": "PAI-CRYPTO",
24 "Unit": "PAI-CRYPTO",
31 "Unit": "PAI-CRYPTO",
38 "Unit": "PAI-CRYPTO",
45 "Unit": "PAI-CRYPTO",
52 "Unit": "PAI-CRYPTO",
59 "Unit": "PAI-CRYPTO",
[all …]
/linux/tools/perf/pmu-events/arch/s390/cf_z17/
H A Dpai_crypto.json3 "Unit": "PAI-CRYPTO",
6 "BriefDescription": "CRYPTO ALL",
10 "Unit": "PAI-CRYPTO",
17 "Unit": "PAI-CRYPTO",
24 "Unit": "PAI-CRYPTO",
31 "Unit": "PAI-CRYPTO",
38 "Unit": "PAI-CRYPTO",
45 "Unit": "PAI-CRYPTO",
52 "Unit": "PAI-CRYPTO",
59 "Unit": "PAI-CRYPTO",
[all …]
/linux/drivers/crypto/caam/
H A Dcompat.h14 #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/sha1.h>
38 #include <crypto/sha2.h>
39 #include <crypto/md5.h>
[all …]
H A DKconfig97 bool "Register algorithm implementations with the Crypto API"
106 Selecting this will offload crypto for users of the
107 scatterlist crypto API (such as the linux native IPSec
111 bool "Queue Interface as Crypto API backend"
121 & receiving crypto jobs to/from CAAM. This gives better performance
128 bool "Register hash algorithm implementations with Crypto API"
134 scatterlist crypto API to the SEC4 via job ring.
137 bool "Register public key cryptography implementations with Crypto API"
155 bool "Register Pseudo random number generation implementation with Crypto API"
160 the Crypto API.
/linux/Documentation/devicetree/bindings/crypto/
H A Dallwinner,sun4i-a10-crypto.yaml4 $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 …]
H A Dallwinner,sun8i-ce.yaml4 $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,sun20i-d1-crypto
18 - allwinner,sun50i-a64-crypto
19 - allwinner,sun50i-h5-crypto
20 - allwinner,sun50i-h6-crypto
21 - allwinner,sun50i-h616-crypto
52 - allwinner,sun20i-d1-crypto
[all …]
H A Drockchip,rk3288-crypto.yaml4 $id: http://devicetree.org/schemas/crypto/rockchip,rk3288-crypto.yaml#
15 - rockchip,rk3288-crypto
16 - rockchip,rk3328-crypto
17 - rockchip,rk3399-crypto
46 const: rockchip,rk3288-crypto
61 - const: crypto-rst
66 const: rockchip,rk3328-crypto
80 - const: crypto-rst
85 const: rockchip,rk3399-crypto
101 - const: crypto-rst
[all …]
H A Dstarfive,jh7110-crypto.yaml4 $id: http://devicetree.org/schemas/crypto/starfive,jh7110-crypto.yaml#
16 - starfive,jh7110-crypto
17 - starfive,jh8100-crypto
66 const: starfive,jh7110-crypto
76 const: starfive,jh8100-crypto
85 crypto: crypto@16000000 {
86 compatible = "starfive,jh7110-crypto";
/linux/kernel/bpf/
H A Dcrypto.c11 #include <crypto/skcipher.h>
18 /* BPF crypto initialization parameters struct */
20 * struct bpf_crypto_params - BPF crypto initialization parameters structure
21 * @type: The string of crypto operation type.
26 * @key: The cipher key used to init crypto algorithm.
43 * struct bpf_crypto_ctx - refcounted BPF crypto context structure
44 * @type: The pointer to bpf crypto type
45 * @tfm: The pointer to instance of crypto API struct.
47 * @rcu: The RCU head used to free the crypto context with RCU safety.
130 * bpf_crypto_ctx_create() - Create a mutable BPF crypto context.
[all …]
/linux/drivers/crypto/ccp/
H A DMakefile19 obj-$(CONFIG_CRYPTO_DEV_CCP_CRYPTO) += ccp-crypto.o
20 ccp-crypto-objs := ccp-crypto-main.o \
21 ccp-crypto-aes.o \
22 ccp-crypto-aes-cmac.o \
23 ccp-crypto-aes-xts.o \
24 ccp-crypto-aes-galois.o \
25 ccp-crypto-des3.o \
26 ccp-crypto-rsa.o \
27 ccp-crypto-sha.o
H A Dccp-crypto.h3 * AMD Cryptographic Coprocessor (CCP) crypto API support
16 #include <crypto/algapi.h>
17 #include <crypto/aes.h>
18 #include <crypto/internal/aead.h>
19 #include <crypto/aead.h>
20 #include <crypto/ctr.h>
21 #include <crypto/hash.h>
22 #include <crypto/sha1.h>
23 #include <crypto/sha2.h>
24 #include <crypto/akcipher.h>
[all …]
/linux/include/crypto/
H A Dhash_info.h11 #include <crypto/sha1.h>
12 #include <crypto/sha2.h>
13 #include <crypto/sha3.h>
14 #include <crypto/md5.h>
15 #include <crypto/streebog.h>
19 /* not defined in include/crypto/ */
25 /* not defined in include/crypto/ */
30 /* not defined in include/crypto/ */
35 /* not defined in include/crypto/ */
/linux/drivers/net/ethernet/chelsio/inline_crypto/
H A DKconfig3 # 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.
48 crypto accelerator. CONFIG_CHELSIO_TLS_DEVICE flag can be enabled
/linux/Documentation/crypto/
H A Dintro.rst1 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 …]
/linux/drivers/crypto/aspeed/
H A DKconfig6 Hash and Crypto Engine (HACE) is designed to accelerate the
13 bool "Enable Aspeed crypto debug messages"
16 Print Aspeed crypto debugging messages if you use this
22 bool "Enable Aspeed Hash & Crypto Engine (HACE) hash"
29 Select here to enable Aspeed Hash & Crypto Engine (HACE)
35 bool "Enable Aspeed Hash & Crypto Engine (HACE) crypto"
43 Select here to enable Aspeed Hash & Crypto Engine (HACE)
44 crypto driver.
/linux/drivers/mmc/host/
H A Dcqhci-crypto.c3 * CQHCI crypto engine (inline encryption) support
8 #include <linux/blk-crypto.h>
9 #include <linux/blk-crypto-profile.h>
12 #include "cqhci-crypto.h"
14 /* Map from blk-crypto modes to CQHCI crypto algorithm IDs and key sizes */
103 * Clear the crypto cfg on the device. Clearing CFGE in cqhci_crypto_clear_keyslot()
122 * The keyslot management operations for CQHCI crypto.
149 * cqhci_crypto_init - initialize CQHCI crypto support
153 * CQHCI_CAP_CS, initialize the crypto support. This involves reading the
154 * crypto capability registers, initializing the blk_crypto_profile, clearing
[all …]
/linux/Documentation/block/
H A Dinline-encryption.rst24 Note that inline encryption hardware is very different from traditional crypto
25 accelerators, which are supported through the kernel crypto API. Traditional
26 crypto accelerators operate on memory regions, whereas inline encryption
28 managed by the block layer, not the kernel crypto API.
41 also want support for falling back to the kernel crypto API when actual inline
45 fall back to crypto API en/decryption).
58 properties the "crypto capabilities". We need a way for device drivers to
59 advertise crypto capabilities to upper layers in a generic way.
67 - Upper layers typically define a specific end-of-life for crypto keys, e.g.
68 when an encrypted directory is locked or when a crypto mapping is torn down.
[all …]
/linux/block/
H A Dblk-crypto-profile.c7 * DOC: blk-crypto profiles
11 * as the way that drivers for inline encryption hardware expose their crypto
14 * construct a crypto profile, then associate it with the disk's request_queue.
25 #define pr_fmt(fmt) "blk-crypto: " fmt
27 #include <linux/blk-crypto-profile.h>
35 #include "blk-crypto-internal.h"
234 * @profile: the crypto profile of the device the key will be used on
339 * __blk_crypto_cfg_supported() - Check whether the given crypto profile
340 * supports the given crypto configuration.
341 * @profile: the crypto profile to check
[all …]
/linux/drivers/crypto/intel/keembay/
H A DKconfig9 Support for Intel Keem Bay Offload and Crypto Subsystem (OCS) AES and
10 SM4 cipher hardware acceleration for use with Crypto API.
23 Support for Intel Keem Bay Offload and Crypto Subsystem (OCS)
24 AES/SM4 ECB mode hardware acceleration for use with Crypto API.
34 Support for Intel Keem Bay Offload and Crypto Subsystem (OCS)
36 Crypto API.
50 Support for Intel Keem Bay Offload and Crypto Subsystem (OCS)
52 Crypto API.
69 Support for Intel Keem Bay Offload and Crypto Subsystem (OCS) Hash
70 Control Unit (HCU) hardware acceleration for use with Crypto API.
/linux/arch/riscv/crypto/
H A DKconfig16 - Zvkned vector crypto extension
18 - Zvkb vector crypto extension (CTR)
19 - Zvkg vector crypto extension (XTS)
29 - Zvkg vector crypto extension
40 - Zvksh vector crypto extension
41 - Zvkb vector crypto extension
57 - Zvksed vector crypto extension
58 - Zvkb vector crypto extension
/linux/Documentation/driver-api/crypto/iaa/
H A Diaa-crypto.rst4 IAA Compression Accelerator Crypto Driver
9 The IAA crypto driver supports compression/decompression compatible
25 represented by selecting the 'deflate-iaa' crypto compression
37 specified by RFC 1951 and is given the crypto algorithm name
49 The IAA crypto driver is available via menuconfig using the following
52 Cryptographic API -> Hardware crypto devices -> Support for Intel(R) IAA Compression Accelerator
56 The IAA crypto driver also supports statistics, which are available
59 …Cryptographic API -> Hardware crypto devices -> Support for Intel(R) IAA Compression -> Enable Int…
140 crypto subsystem by removing and reinserting the iaa_crypto module.
182 … --mode=dedicated --type=kernel --priority=10 --name="iaa_crypto" --driver-name="crypto" iax1/wq1.0
[all …]
/linux/drivers/crypto/allwinner/
H A DKconfig6 Say Y here to get to see options for Allwinner hardware crypto devices
19 Some Allwinner SoC have a crypto accelerator named
45 tristate "Support for Allwinner Crypto Engine cryptographic offloader"
55 Select y here to have support for the crypto Engine available on
57 The Crypto Engine handle AES/3DES ciphers in ECB/CBC mode.
82 bool "Support for Allwinner Crypto Engine PRNG"
87 the Pseudo-Random Number Generator found in the Crypto Engine.
90 bool "Support for Allwinner Crypto Engine TRNG"
95 the True Random Number Generator found in the Crypto Engine.
/linux/drivers/ufs/core/
H A Dufshcd-crypto.c7 #include "ufshcd-crypto.h"
9 /* Blk-crypto modes supported by UFS crypto */
94 * Clear the crypto cfg on the device. Clearing CFGE in ufshcd_crypto_keyslot_evict()
142 * ufshcd_hba_init_crypto_capabilities - Read crypto capabilities, init crypto
146 * Return: 0 if crypto was initialized or is not supported, else a -errno value.
158 * Don't use crypto if either the hardware doesn't advertise the in ufshcd_hba_init_crypto_capabilities()
159 * standard crypto capability bit *or* if the vendor specific driver in ufshcd_hba_init_crypto_capabilities()
160 * hasn't advertised that crypto is supported. in ufshcd_hba_init_crypto_capabilities()
192 * Cache all the UFS crypto capabilities and advertise the supported in ufshcd_hba_init_crypto_capabilities()
193 * crypto modes and data unit sizes to the block layer. in ufshcd_hba_init_crypto_capabilities()
[all …]
/linux/fs/crypto/
H A Dinline_crypt.c10 * as part of the bio, instead of the filesystem doing the crypto itself via
11 * crypto API. See Documentation/block/inline-encryption.rst. fscrypt still
15 #include <linux/blk-crypto.h>
64 * Log a message when starting to use blk-crypto (native) or blk-crypto-fallback
65 * for an encryption mode for the first time. This is the blk-crypto
66 * counterpart to the message logged when starting to use the crypto API for the
83 pr_info("fscrypt: %s using blk-crypto (native)\n", in fscrypt_log_blk_crypto_impl()
86 pr_info("fscrypt: %s using blk-crypto-fallback\n", in fscrypt_log_blk_crypto_impl()
107 /* The crypto mode must have a blk-crypto counterpart */ in fscrypt_select_encryption_impl()
129 * On all the filesystem's block devices, blk-crypto must support the in fscrypt_select_encryption_impl()
[all …]
/linux/drivers/crypto/cavium/nitrox/
H A Dnitrox_aead.c4 #include <linux/crypto.h>
7 #include <crypto/aead.h>
8 #include <crypto/authenc.h>
9 #include <crypto/des.h>
10 #include <crypto/internal/aead.h>
11 #include <crypto/scatterwalk.h>
12 #include <crypto/gcm.h>
45 /* fill crypto context */ in nitrox_aes_gcm_setkey()
52 memset(&fctx->crypto, 0, sizeof(fctx->crypto)); in nitrox_aes_gcm_setkey()
53 memcpy(fctx->crypto.u.key, key, keylen); in nitrox_aes_gcm_setkey()
[all …]

12345678910>>...45