Home
last modified time | relevance | path

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

12345678910>>...128

/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/s390/cf_z16/
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 …]
/kernel/linux/linux-6.6/drivers/crypto/caam/
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 …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/crypto/
Dmarvell-cesa.txt5 "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 …]
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 …]
Dmv_cesa.txt5 "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 …]
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 …]
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
51 - allwinner,sun20i-d1-crypto
62 const: allwinner,sun50i-h6-crypto
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/crypto/
Dmarvell-cesa.txt5 "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 …]
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 …]
Dmv_cesa.txt5 "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 …]
/kernel/linux/linux-5.10/drivers/crypto/caam/
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/sha.h>
38 #include <crypto/md5.h>
39 #include <crypto/chacha.h>
[all …]
/kernel/linux/linux-6.6/drivers/crypto/virtio/
Dvirtio_crypto_mgr.c2 /* 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 …]
/kernel/linux/linux-5.10/drivers/crypto/virtio/
Dvirtio_crypto_mgr.c2 /* 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 …]
/kernel/linux/linux-6.6/arch/arm64/crypto/
DKconfig6 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 …]
/kernel/linux/linux-6.6/drivers/crypto/
DKconfig4 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
73 s390 cryptographic adapters like Crypto Express 4 up
87 and queues and some flags on crypto requests are interpreted as
155 tristate "Storlink SL3516 crypto offloader"
164 This option allows you to have support for SL3516 crypto offloader.
176 tristate "Driver HIFN 795x crypto accelerator chips"
183 This option allows you to have support for HIFN 795x crypto adapters.
[all …]
/kernel/linux/linux-6.6/drivers/virt/coco/sev-guest/
Dsev-guest.c19 #include <crypto/aead.h>
48 struct snp_guest_crypto *crypto; member
162 struct snp_guest_crypto *crypto; in init_crypto() local
164 crypto = kzalloc(sizeof(*crypto), GFP_KERNEL_ACCOUNT); in init_crypto()
165 if (!crypto) in init_crypto()
168 crypto->tfm = crypto_alloc_aead("gcm(aes)", 0, 0); in init_crypto()
169 if (IS_ERR(crypto->tfm)) in init_crypto()
172 if (crypto_aead_setkey(crypto->tfm, key, keylen)) in init_crypto()
175 crypto->iv_len = crypto_aead_ivsize(crypto->tfm); in init_crypto()
176 crypto->iv = kmalloc(crypto->iv_len, GFP_KERNEL_ACCOUNT); in init_crypto()
[all …]
/kernel/linux/linux-5.10/drivers/crypto/
DKconfig4 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 …]
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Ddebugfs-hisi-hpre3 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 …]
Ddebugfs-hisi-zip3 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 …]
Ddebugfs-hisi-sec3 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 …]
/kernel/linux/linux-6.6/Documentation/block/
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 …]
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Ddebugfs-hisi-hpre3 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 …]
/kernel/linux/linux-5.10/drivers/crypto/ccp/
DMakefile15 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
/kernel/linux/linux-6.6/drivers/crypto/ccp/
DMakefile17 obj-$(CONFIG_CRYPTO_DEV_CCP_CRYPTO) += ccp-crypto.o
18 ccp-crypto-objs := ccp-crypto-main.o \
19 ccp-crypto-aes.o \
20 ccp-crypto-aes-cmac.o \
21 ccp-crypto-aes-xts.o \
22 ccp-crypto-aes-galois.o \
23 ccp-crypto-des3.o \
24 ccp-crypto-rsa.o \
25 ccp-crypto-sha.o
/kernel/linux/linux-6.6/drivers/staging/rtl8192e/
DKconfig19 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.

12345678910>>...128