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.
74 s390 cryptographic adapters like Crypto Express 4 up
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
91 - A pkey pckmo kernel module (pkey-pckmo.ko) which is automatically
94 - A pkey CCA kernel module (pkey-cca.ko) which is automatically
95 loaded when a CEX crypto card is available.
96 - A pkey EP11 kernel module (pkey-ep11.ko) which is automatically
97 loaded when a CEX crypto card is available.
98 - A pkey UV kernel module (pkey-uv.ko) which is automatically
114 The PKEY CCA support handler needs a Crypto Express card (CEX)
130 The PKEY EP11 support handler needs a Crypto Express card (CEX)
144 The PCKMO instruction can be enabled and disabled in the crypto
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.
204 tristate "Storlink SL3516 crypto offloader"
213 This option allows you to have support for SL3516 crypto offloader.
225 tristate "Driver HIFN 795x crypto accelerator chips"
232 This option allows you to have support for HIFN 795x crypto adapters.
239 on the HIFN 795x crypto adapters.
241 source "drivers/crypto/caam/Kconfig"
244 tristate "Talitos Freescale Security Engine (SEC)"
253 Say 'Y' here to use the Freescale Security Engine (SEC)
268 Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0
269 found on MPC82xx or the Freescale Security Engine (SEC Lite)
277 Say 'Y' here to use the Freescale Security Engine (SEC)
281 tristate "Driver AMCC PPC4xx crypto accelerator"
292 This option allows you to have support for AMCC crypto acceleration.
299 This option provides the kernel-side support for the TRNG hardware
303 tristate "Support for OMAP crypto HW accelerators"
306 OMAP processors have various crypto HW accelerators. Select this if
307 you want to use the OMAP modules for any of the crypto algorithms.
325 tristate "Support for OMAP AES hw engine"
339 tristate "Support for OMAP DES/3DES hw engine"
353 tristate "Support for SAHARA crypto accelerator"
360 This option enables support for the SAHARA HW crypto accelerator
369 This driver provides kernel-side support through the
374 module will be called exynos-rng.
379 tristate "Support for Samsung S5PV210/Exynos crypto accelerator"
385 This option allows you to have support for S5P crypto acceleration.
399 needed for small and zero-size messages.
413 source "drivers/crypto/nx/Kconfig"
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.
509 source "drivers/crypto/ccp/Kconfig"
523 co-processor on the die.
526 will be called mxs-dcp.
528 source "drivers/crypto/cavium/cpt/Kconfig"
529 source "drivers/crypto/cavium/nitrox/Kconfig"
530 source "drivers/crypto/marvell/Kconfig"
531 source "drivers/crypto/intel/Kconfig"
541 tristate "Qualcomm crypto engine accelerator"
545 This driver supports Qualcomm crypto engine accelerator
578 (default), hashes-only, or skciphers-only.
580 The QCE engine does not appear to scale as well as the CPU to handle
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))
634 using software instead of the crypto engine. It can be changed by
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.
647 Note that 192-bit keys are not supported by the hardware and are
661 module will be called qcom-rng. If unsure, say N.
669 #source "drivers/crypto/vmx/Kconfig"
684 tristate "Rockchip's Cryptographic Engine driver"
700 This driver interfaces with the hardware crypto accelerator.
704 bool "Enable Rockchip crypto stats"
708 Say y to enable Rockchip crypto debug stats.
713 tristate "Enable Tegra Security Engine"
718 Select this to enable Tegra Security Engine which accelerates various
728 Xilinx ZynqMP has AES-GCM engine used for symmetric key
738 Xilinx ZynqMP has SHA3 engine used for secure hash calculation.
739 This driver interfaces with SHA3 hardware engine.
743 source "drivers/crypto/chelsio/Kconfig"
745 source "drivers/crypto/virtio/Kconfig"
748 tristate "Broadcom symmetric crypto/hash acceleration support"
759 This driver provides support for Broadcom crypto acceleration using the
763 source "drivers/crypto/stm32/Kconfig"
766 tristate "Inside Secure's SafeXcel cryptographic engine driver"
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
808 depends on CRYPTO && CRYPTO_HW && OF && HAS_DMA
835 source "drivers/crypto/hisilicon/Kconfig"
837 source "drivers/crypto/amlogic/Kconfig"
852 K3 devices include a security accelerator engine that may be
853 used for crypto offload. Select this if you want to use hardware
856 source "drivers/crypto/aspeed/Kconfig"
857 source "drivers/crypto/starfive/Kconfig"