| /linux-6.12.1/tools/perf/pmu-events/arch/s390/cf_z16/ |
| D | pai_crypto.json | 3 "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-6.12.1/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/sha1.h>
38 #include <crypto/sha2.h>
39 #include <crypto/md5.h>
[all …]
|
| /linux-6.12.1/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 | qcom,inline-crypto-engine.yaml | 4 $id: http://devicetree.org/schemas/crypto/qcom,inline-crypto-engine.yaml#
7 title: Qualcomm Technologies, Inc. (QTI) Inline Crypto Engine
16 - qcom,sa8775p-inline-crypto-engine
17 - qcom,sc7180-inline-crypto-engine
18 - qcom,sc7280-inline-crypto-engine
19 - qcom,sm8450-inline-crypto-engine
20 - qcom,sm8550-inline-crypto-engine
21 - qcom,sm8650-inline-crypto-engine
22 - const: qcom,inline-crypto-engine
41 crypto@1d88000 {
[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,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 …]
|
| D | rockchip,rk3288-crypto.yaml | 4 $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 …]
|
| /linux-6.12.1/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-6.12.1/arch/arm64/crypto/ |
| D | Kconfig | 6 tristate "Hash functions: GHASH (ARMv8 Crypto Extensions)"
16 - ARMv8 Crypto Extensions
40 tristate "Hash functions: SHA-1 (ARMv8 Crypto Extensions)"
48 - ARMv8 Crypto Extensions
59 tristate "Hash functions: SHA-224 and SHA-256 (ARMv8 Crypto Extensions)"
67 - ARMv8 Crypto Extensions
78 tristate "Hash functions: SHA-384 and SHA-512 (ARMv8 Crypto Extensions)"
86 - ARMv8 Crypto Extensions
89 tristate "Hash functions: SHA-3 (ARMv8.2 Crypto Extensions)"
97 - ARMv8.2 Crypto Extensions
[all …]
|
| /linux-6.12.1/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 s390 cryptographic adapters like Crypto Express 4 up
89 and the sysfs API and the in-kernel API to the crypto cipher
95 loaded when a CEX crypto card is available.
97 loaded when a CEX crypto card is available.
111 The PKEY CCA support handler needs a Crypto Express card (CEX)
127 The PKEY EP11 support handler needs a Crypto Express card (CEX)
[all …]
|
| /linux-6.12.1/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
42 Contact: linux-crypto@vger.kernel.org
48 Contact: linux-crypto@vger.kernel.org
55 Contact: linux-crypto@vger.kernel.org
62 Contact: linux-crypto@vger.kernel.org
71 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
41 Contact: linux-crypto@vger.kernel.org
48 Contact: linux-crypto@vger.kernel.org
55 Contact: linux-crypto@vger.kernel.org
64 Contact: linux-crypto@vger.kernel.org
71 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
29 Contact: linux-crypto@vger.kernel.org
36 Contact: linux-crypto@vger.kernel.org
43 Contact: linux-crypto@vger.kernel.org
51 Contact: linux-crypto@vger.kernel.org
58 Contact: linux-crypto@vger.kernel.org
64 Contact: linux-crypto@vger.kernel.org
70 Contact: linux-crypto@vger.kernel.org
[all …]
|
| /linux-6.12.1/Documentation/block/ |
| D | inline-encryption.rst | 24 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-6.12.1/arch/riscv/crypto/ |
| D | Kconfig | 16 - Zvkned vector crypto extension
18 - Zvkb vector crypto extension (CTR)
19 - Zvkg vector crypto extension (XTS)
30 - Zvkb vector crypto extension
40 - Zvkg vector crypto extension
50 - Zvknha or Zvknhb vector crypto extensions
51 - Zvkb vector crypto extension
61 - Zvknhb vector crypto extension
62 - Zvkb vector crypto extension
73 - Zvksh vector crypto extension
[all …]
|
| /linux-6.12.1/drivers/crypto/ccp/ |
| D | Makefile | 18 obj-$(CONFIG_CRYPTO_DEV_CCP_CRYPTO) += ccp-crypto.o
19 ccp-crypto-objs := ccp-crypto-main.o \
20 ccp-crypto-aes.o \
21 ccp-crypto-aes-cmac.o \
22 ccp-crypto-aes-xts.o \
23 ccp-crypto-aes-galois.o \
24 ccp-crypto-des3.o \
25 ccp-crypto-rsa.o \
26 ccp-crypto-sha.o
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/kernel/bpf/ |
| D | crypto.c | 11 #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-6.12.1/drivers/staging/rtl8192e/ |
| D | Kconfig | 19 tristate "Support for rtllib CCMP crypto"
21 select CRYPTO
26 CCMP crypto driver for rtllib.
29 Adds support for the CCM mode Protocol crypto driver for
33 tristate "Support for rtllib TKIP crypto"
35 select CRYPTO
40 TKIP crypto driver for rtllib.
47 tristate "Support for rtllib WEP crypto"
52 WEP crypto driver for rtllib.
56 (WEP) crypto protocol for wireless cards.
|
| /linux-6.12.1/drivers/virt/coco/sev-guest/ |
| D | sev-guest.c | 20 #include <crypto/aead.h>
53 struct snp_guest_crypto *crypto; member
174 struct snp_guest_crypto *crypto; in init_crypto() local
176 crypto = kzalloc(sizeof(*crypto), GFP_KERNEL_ACCOUNT); in init_crypto()
177 if (!crypto) in init_crypto()
180 crypto->tfm = crypto_alloc_aead("gcm(aes)", 0, 0); in init_crypto()
181 if (IS_ERR(crypto->tfm)) in init_crypto()
184 if (crypto_aead_setkey(crypto->tfm, key, keylen)) in init_crypto()
187 crypto->iv_len = crypto_aead_ivsize(crypto->tfm); in init_crypto()
188 crypto->iv = kmalloc(crypto->iv_len, GFP_KERNEL_ACCOUNT); in init_crypto()
[all …]
|
| /linux-6.12.1/include/crypto/ |
| D | hash_info.h | 11 #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-6.12.1/block/ |
| D | blk-crypto-profile.c | 7 * 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-6.12.1/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.
48 crypto accelerator. CONFIG_CHELSIO_TLS_DEVICE flag can be enabled
|
| /linux-6.12.1/drivers/crypto/aspeed/ |
| D | Kconfig | 6 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.
|