Searched full:crypto (Results 1 – 25 of 138) sorted by relevance
123456
| /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 | 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,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 | 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 …]
|
| D | starfive,jh7110-crypto.yaml | 4 $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";
|
| D | brcm,spu-crypto.txt | 7 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";
|
| D | artpec6-crypto.txt | 1 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";
|
| D | amlogic,gxl-crypto.yaml | 4 $id: http://devicetree.org/schemas/crypto/amlogic,gxl-crypto.yaml#
15 - const: amlogic,gxl-crypto
46 crypto: crypto-engine@c883e000 {
47 compatible = "amlogic,gxl-crypto";
|
| D | mediatek-crypto.txt | 4 - 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";
|
| D | allwinner,sun8i-ss.yaml | 4 $id: http://devicetree.org/schemas/crypto/allwinner,sun8i-ss.yaml#
15 - allwinner,sun8i-a83t-crypto
16 - allwinner,sun9i-a80-crypto
53 crypto: crypto@1c15000 {
54 compatible = "allwinner,sun8i-a83t-crypto";
|
| D | intel,ixp4xx-crypto.yaml | 5 $id: http://devicetree.org/schemas/crypto/intel,ixp4xx-crypto.yaml#
16 it is defined as a subnode of the NPE, if crypto support is
21 const: intel,ixp4xx-crypto
27 - description: phandle to the NPE this crypto engine
29 description: phandle to the NPE this crypto engine is using, the cell
|
| D | cortina,sl3516-crypto.yaml | 4 $id: http://devicetree.org/schemas/crypto/cortina,sl3516-crypto.yaml#
15 - cortina,sl3516-crypto
44 crypto@62000000 {
45 compatible = "cortina,sl3516-crypto";
|
| D | qcom-qce.yaml | 4 $id: http://devicetree.org/schemas/crypto/qcom-qce.yaml#
7 title: Qualcomm crypto engine driver
13 This document defines the binding for the QCE crypto
19 - const: qcom,crypto-v5.1
23 - const: qcom,crypto-v5.4
77 Interconnect path between qce crypto and main memory.
98 - qcom,crypto-v5.1
99 - qcom,crypto-v5.4
158 crypto-engine@fd45a000 {
|
| D | aspeed,ast2500-hace.yaml | 4 $id: http://devicetree.org/schemas/crypto/aspeed,ast2500-hace.yaml#
7 title: ASPEED HACE hash and crypto Hardware Accelerator Engines
13 The Hash and Crypto Engine (HACE) is designed to accelerate the throughput
15 divided into two independently engines - Hash Engine and Crypto Engine.
47 hace: crypto@1e6d0000 {
|
| /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 …]
|
| /Documentation/crypto/ |
| 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/crypto/internal/cipher.h
34 .. kernel-doc:: include/crypto/internal/cipher.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
|
| 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 | api-rng.rst | 4 .. kernel-doc:: include/crypto/rng.h
7 Crypto API Random Number API
10 .. kernel-doc:: include/crypto/rng.h
13 .. kernel-doc:: include/crypto/rng.h
|
123456