Lines Matching +full:hardware +full:- +full:protected
1 # SPDX-License-Identifier: GPL-2.0-only
4 bool "Hardware crypto devices"
7 Say Y here to get to see options for hardware crypto devices and
39 called padlock-aes.
53 called padlock-sha.
61 Say 'Y' here to use the AMD Geode LX processor on-board AES
65 will be called geode-aes.
79 tristate "Kernel API for protected key handling"
83 for creation and handling of protected keys. Other parts of the
86 The protected key support is distributed into:
87 - A pkey base and API kernel module (pkey.ko) which offers the
89 and the sysfs API and the in-kernel API to the crypto cipher
90 implementations using protected key.
91 - A pkey pckmo kernel module (pkey-pckmo.ko) which is automatically
92 loaded when pckmo support (that is generation of protected keys
94 - A pkey CCA kernel module (pkey-cca.ko) which is automatically
96 - A pkey EP11 kernel module (pkey-ep11.ko) which is automatically
98 - A pkey UV kernel module (pkey-uv.ko) which is automatically
100 protected execution environment.
103 API for protected key handling.
110 This is the CCA support handler for deriving protected keys
112 way to make protected keys from clear key values.
118 this option unless you are sure you never need to derive protected
126 This is the EP11 support handler for deriving protected keys
128 way to make protected keys from clear key values.
134 this option unless you are sure you never need to derive protected
141 This is the PCKMO support handler for deriving protected keys
149 The PCKMO way of deriving protected keys from clear key material
150 is especially used during self test of protected key ciphers like
152 generate protected keys from clear key values.
155 this option unless you are sure you never need to derive protected
163 This is the PKEY Ultravisor support handler for deriving protected
167 retrieval of protected keys from secrets stored within the
169 a protected execution guest and thus this module will fail upon
170 modprobe if no protected execution environment is detected.
173 guest with protected execution and you want to use UV retrievable
184 This is the s390 hardware accelerated implementation of the
185 AES cipher algorithms for use with protected key.
188 for example to use protected key encrypted devices.
197 and uses triple-DES to generate secure random numbers like the
198 ANSI X9.17 standard. User-space programs access the
199 pseudo-random-number device through the char device /dev/prandom.
299 This option provides the kernel-side support for the TRNG hardware
369 This driver provides kernel-side support through the
370 cryptographic API for the pseudo random number generator hardware
374 module will be called exynos-rng.
399 needed for small and zero-size messages.
407 This enables support for the NX hardware cryptographic accelerator
440 will be called atmel-aes.
453 will be called atmel-tdes.
466 will be called atmel-sha.
484 will be called atmel-ecc.
499 will be called atmel-sha204a.
523 co-processor on the die.
526 will be called mxs-dcp.
546 hardware. To compile this driver as a module, choose M here. The
578 (default), hashes-only, or skciphers-only.
581 multiple crypto requests. While the ipq40xx chips have 4-core CPUs, the
585 algorithms, sharing the load with the CPU. Enabling skciphers-only
595 - AES (CBC, CTR, ECB, XTS)
596 - 3DES (CBC, ECB)
597 - DES (CBC, ECB)
598 - SHA1, HMAC-SHA1
599 - SHA256, HMAC-SHA256
602 bool "Symmetric-key ciphers only"
605 Enable symmetric-key ciphers only:
606 - AES (CBC, CTR, ECB, XTS)
607 - 3DES (ECB, CBC)
608 - DES (ECB, CBC)
615 - SHA1, HMAC-SHA1
616 - SHA256, HMAC-SHA256
623 - authenc()
624 - ccm(aes)
625 - rfc4309(ccm(aes))
637 Small blocks are processed faster in software than hardware.
638 Considering the 256-bit ciphers, software is 2-3 times faster than
639 qce at 256-bytes, 30% faster at 512, and about even at 768-bytes.
640 With 128-bit keys, the break-even point would be around 1024-bytes.
643 cost in CPU usage. The minimum recommended setting is 16-bytes
644 (1 AES block), since AES-GCM will fail if you set it lower.
645 Setting this to zero will send all requests to the hardware.
647 Note that 192-bit keys are not supported by the hardware and are
649 are done by the hardware.
658 Generator hardware found on Qualcomm SoCs.
661 module will be called qcom-rng. If unsure, say N.
672 tristate "Imagination Technologies hardware hash accelerator"
680 hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256
700 This driver interfaces with the hardware crypto accelerator.
728 Xilinx ZynqMP has AES-GCM engine used for symmetric key
734 tristate "Support for Xilinx ZynqMP SHA3 hardware accelerator"
739 This driver interfaces with SHA3 hardware engine.
781 This driver interfaces with the SafeXcel EIP-97 and EIP-197 cryptographic
785 Additionally, it accelerates combined AES-CBC/HMAC-SHA AEAD operations.
788 tristate "Support for Axis ARTPEC-6/7 hardware crypto acceleration."
801 Enables the driver for the on-chip crypto accelerator
831 Choose this if you wish to use hardware acceleration of
853 used for crypto offload. Select this if you want to use hardware
858 source "drivers/crypto/inside-secure/eip93/Kconfig"