Lines Matching +full:crypto +full:- +full:engine
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
14 source "drivers/crypto/allwinner/Kconfig"
20 Some VIA processors come with an integrated crypto engine
21 (so called VIA PadLock ACE, Advanced Cryptography Engine)
39 called padlock-aes.
53 called padlock-sha.
56 tristate "Support for the Geode LX AES engine"
61 Say 'Y' here to use the AMD Geode LX processor on-board AES
62 engine for the CryptoAPI AES algorithm.
65 will be called geode-aes.
73 s390 cryptographic adapters like Crypto Express 4 up
87 and queues and some flags on crypto requests are interpreted as
131 and uses triple-DES to generate secure random numbers like the
132 ANSI X9.17 standard. User-space programs access the
133 pseudo-random-number device through the char device /dev/prandom.
149 sub-units. One set provides the Modular Arithmetic Unit,
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.
190 on the HIFN 795x crypto adapters.
192 source "drivers/crypto/caam/Kconfig"
195 tristate "Talitos Freescale Security Engine (SEC)"
204 Say 'Y' here to use the Freescale Security Engine (SEC)
219 Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0
220 found on MPC82xx or the Freescale Security Engine (SEC Lite)
228 Say 'Y' here to use the Freescale Security Engine (SEC)
232 tristate "Driver AMCC PPC4xx crypto accelerator"
243 This option allows you to have support for AMCC crypto acceleration.
250 This option provides the kernel-side support for the TRNG hardware
254 tristate "Support for OMAP crypto HW accelerators"
257 OMAP processors have various crypto HW accelerators. Select this if
258 you want to use the OMAP modules for any of the crypto algorithms.
276 tristate "Support for OMAP AES hw engine"
290 tristate "Support for OMAP DES/3DES hw engine"
304 tristate "Support for SAHARA crypto accelerator"
310 This option enables support for the SAHARA HW crypto accelerator
319 This driver provides kernel-side support through the
324 module will be called exynos-rng.
329 tristate "Support for Samsung S5PV210/Exynos crypto accelerator"
335 This option allows you to have support for S5P crypto acceleration.
349 needed for small and zero-size messages.
363 source "drivers/crypto/nx/Kconfig"
390 will be called atmel-aes.
403 will be called atmel-tdes.
416 will be called atmel-sha.
434 will be called atmel-ecc.
449 will be called atmel-sha204a.
459 source "drivers/crypto/ccp/Kconfig"
473 co-processor on the die.
476 will be called mxs-dcp.
478 source "drivers/crypto/cavium/cpt/Kconfig"
479 source "drivers/crypto/cavium/nitrox/Kconfig"
480 source "drivers/crypto/marvell/Kconfig"
481 source "drivers/crypto/intel/Kconfig"
491 tristate "Qualcomm crypto engine accelerator"
495 This driver supports Qualcomm crypto engine accelerator
528 (default), hashes-only, or skciphers-only.
530 The QCE engine does not appear to scale as well as the CPU to handle
531 multiple crypto requests. While the ipq40xx chips have 4-core CPUs, the
535 algorithms, sharing the load with the CPU. Enabling skciphers-only
545 - AES (CBC, CTR, ECB, XTS)
546 - 3DES (CBC, ECB)
547 - DES (CBC, ECB)
548 - SHA1, HMAC-SHA1
549 - SHA256, HMAC-SHA256
552 bool "Symmetric-key ciphers only"
555 Enable symmetric-key ciphers only:
556 - AES (CBC, CTR, ECB, XTS)
557 - 3DES (ECB, CBC)
558 - DES (ECB, CBC)
565 - SHA1, HMAC-SHA1
566 - SHA256, HMAC-SHA256
573 - authenc()
574 - ccm(aes)
575 - rfc4309(ccm(aes))
584 using software instead of the crypto engine. It can be changed by
588 Considering the 256-bit ciphers, software is 2-3 times faster than
589 qce at 256-bytes, 30% faster at 512, and about even at 768-bytes.
590 With 128-bit keys, the break-even point would be around 1024-bytes.
593 cost in CPU usage. The minimum recommended setting is 16-bytes
594 (1 AES block), since AES-GCM will fail if you set it lower.
597 Note that 192-bit keys are not supported by the hardware and are
610 module will be called qcom-rng. If unsure, say N.
618 source "drivers/crypto/vmx/Kconfig"
633 tristate "Rockchip's Cryptographic Engine driver"
649 This driver interfaces with the hardware crypto accelerator.
653 bool "Enable Rockchip crypto stats"
657 Say y to enable Rockchip crypto debug stats.
669 Xilinx ZynqMP has AES-GCM engine used for symmetric key
679 Xilinx ZynqMP has SHA3 engine used for secure hash calculation.
680 This driver interfaces with SHA3 hardware engine.
684 source "drivers/crypto/chelsio/Kconfig"
686 source "drivers/crypto/virtio/Kconfig"
689 tristate "Broadcom symmetric crypto/hash acceleration support"
700 This driver provides support for Broadcom crypto acceleration using the
704 source "drivers/crypto/stm32/Kconfig"
707 tristate "Inside Secure's SafeXcel cryptographic engine driver"
722 This driver interfaces with the SafeXcel EIP-97 and EIP-197 cryptographic
726 Additionally, it accelerates combined AES-CBC/HMAC-SHA AEAD operations.
729 tristate "Support for Axis ARTPEC-6/7 hardware crypto acceleration."
742 Enables the driver for the on-chip crypto accelerator
749 depends on CRYPTO && CRYPTO_HW && OF && HAS_DMA
776 source "drivers/crypto/hisilicon/Kconfig"
778 source "drivers/crypto/amlogic/Kconfig"
793 K3 devices include a security accelerator engine that may be
794 used for crypto offload. Select this if you want to use hardware
797 source "drivers/crypto/aspeed/Kconfig"
798 source "drivers/crypto/starfive/Kconfig"