Home
last modified time | relevance | path

Searched refs:crypto (Results 1 – 25 of 381) sorted by relevance

12345678910>>...16

/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 …]
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-crypto.txt4 - 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";
Dbrcm,spu-crypto.txt7 brcm,spum-crypto - for devices with SPU-M hardware
8 brcm,spu2-crypto - for devices with SPU2 hardware
9 brcm,spu2-v2-crypto - for devices with enhanced SPU2 hardware features like SHA3
11 brcm,spum-nsp-crypto - for the Northstar Plus variant of the SPU-M hardware
18 crypto@612d0000 {
19 compatible = "brcm,spum-crypto";
Dartpec6-crypto.txt1 Axis crypto engine with PDMA interface.
5 "axis,artpec6-crypto" for the version in the Axis ARTPEC-6 SoC
6 "axis,artpec7-crypto" for the version in the Axis ARTPEC-7 SoC.
12 crypto@f4264000 {
13 compatible = "axis,artpec6-crypto";
Dmediatek-crypto.txt4 - compatible: Should be "mediatek,eip97-crypto"
6 - interrupts: Should contain the five crypto engines interrupts in numeric
14 crypto: crypto@1b240000 {
15 compatible = "mediatek,eip97-crypto";
Dqcom-qce.txt1 Qualcomm crypto engine driver
5 - compatible : should be "qcom,crypto-v5.1"
10 "core" clocks rest of the crypto block
16 crypto@fd45a000 {
17 compatible = "qcom,crypto-v5.1";
/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-5.10/Documentation/crypto/
Dapi-skcipher.rst4 .. 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
Dapi-digest.rst4 .. 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
Dapi-kpp.rst4 .. 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
Dapi-aead.rst4 .. kernel-doc:: include/crypto/aead.h
7 .. kernel-doc:: include/crypto/aead.h
13 .. kernel-doc:: include/crypto/aead.h
19 .. kernel-doc:: include/crypto/aead.h
22 .. kernel-doc:: include/crypto/aead.h
Dintro.rst7 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
51 transformation. Transformation object is allocated when a crypto API
Dapi-akcipher.rst4 .. kernel-doc:: include/crypto/akcipher.h
10 .. kernel-doc:: include/crypto/akcipher.h
13 .. kernel-doc:: include/crypto/akcipher.h
19 .. kernel-doc:: include/crypto/akcipher.h
Darchitecture.rst7 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
74 must provide a callback function the kernel crypto API can invoke to
[all …]
Dapi-rng.rst4 .. kernel-doc:: include/crypto/rng.h
10 .. kernel-doc:: include/crypto/rng.h
13 .. kernel-doc:: include/crypto/rng.h
/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 …]
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
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 …]
Ddebugfs-hisi-sec3 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 …]
/kernel/linux/linux-5.10/drivers/net/wireless/ralink/rt2x00/
Drt2x00mac.c437 static void memcpy_tkip(struct rt2x00lib_crypto *crypto, u8 *key, u8 key_len) in memcpy_tkip() argument
440 memcpy(crypto->key, in memcpy_tkip()
442 sizeof(crypto->key)); in memcpy_tkip()
445 memcpy(crypto->tx_mic, in memcpy_tkip()
447 sizeof(crypto->tx_mic)); in memcpy_tkip()
450 memcpy(crypto->rx_mic, in memcpy_tkip()
452 sizeof(crypto->rx_mic)); in memcpy_tkip()
461 struct rt2x00lib_crypto *crypto, in rt2x00mac_set_key()
463 struct rt2x00lib_crypto crypto; in rt2x00mac_set_key() local
486 memset(&crypto, 0, sizeof(crypto)); in rt2x00mac_set_key()
[all …]
/kernel/linux/linux-5.10/drivers/net/ethernet/chelsio/inline_crypto/
DKconfig3 # Chelsio inline crypto configuration
11 Enable support for inline crypto.
12 Allows enable/disable from list of inline crypto drivers.
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
/kernel/linux/linux-5.10/drivers/staging/rtl8192e/
DKconfig15 tristate "Support for rtllib CCMP crypto"
22 CCMP crypto driver for rtllib.
27 tristate "Support for rtllib TKIP crypto"
34 TKIP crypto driver for rtllib.
39 tristate "Support for rtllib WEP crypto"
44 TKIP crypto driver for rtllib.
/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
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"
277 This option allows you to have support for HIFN 795x crypto adapters.
284 on the HIFN 795x crypto adapters.
286 source "drivers/crypto/caam/Kconfig"
[all …]
/kernel/linux/linux-5.10/Documentation/block/
Dinline-encryption.rst27 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 …]
/kernel/linux/linux-5.10/drivers/crypto/ux500/
DKconfig8 tristate "UX500 crypto driver for CRYP block"
14 This selects the crypto driver for the UX500_CRYP hardware. It supports
18 tristate "UX500 crypto driver for HASH block"
28 bool "Activate ux500 platform debug-mode for crypto and hash block"

12345678910>>...16