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
8 processors. This option alone does not add any kernel code.
10 If you say N, all options in this submenu will be skipped and disabled.
14 config CRYPTO_DEV_PADLOCK
15 tristate "Support for VIA PadLock ACE"
16 depends on X86 && !UML
18 Some VIA processors come with an integrated crypto engine
19 (so called VIA PadLock ACE, Advanced Cryptography Engine)
20 that provides instructions for very fast cryptographic
21 operations with supported algorithms.
23 The instructions are used only when the CPU supports them.
24 Otherwise software encryption is used.
26 config CRYPTO_DEV_PADLOCK_AES
27 tristate "PadLock driver for AES algorithm"
28 depends on CRYPTO_DEV_PADLOCK
29 select CRYPTO_BLKCIPHER
32 Use VIA PadLock for AES algorithm.
34 Available in VIA C3 and newer CPUs.
36 If unsure say M. The compiled module will be
39 config CRYPTO_DEV_PADLOCK_SHA
40 tristate "PadLock driver for SHA1 and SHA256 algorithms"
41 depends on CRYPTO_DEV_PADLOCK
46 Use VIA PadLock for SHA1/SHA256 algorithms.
48 Available in VIA C7 and newer processors.
50 If unsure say M. The compiled module will be
53 config CRYPTO_DEV_GEODE
54 tristate "Support for the Geode LX AES engine"
55 depends on X86_32 && PCI
57 select CRYPTO_BLKCIPHER
59 Say 'Y' here to use the AMD Geode LX processor on-board AES
60 engine for the CryptoAPI AES algorithm.
62 To compile this driver as a module, choose M here: the module
63 will be called geode-aes.
66 tristate "Support for s390 cryptographic adapters"
70 Select this option if you want to enable support for
71 s390 cryptographic adapters like:
72 + PCI-X Cryptographic Coprocessor (PCIXCC)
73 + Crypto Express 2,3,4 or 5 Coprocessor (CEXxC)
74 + Crypto Express 2,3,4 or 5 Accelerator (CEXxA)
75 + Crypto Express 4 or 5 EP11 Coprocessor (CEXxP)
77 config ZCRYPT_MULTIDEVNODES
78 bool "Support for multiple zcrypt device nodes"
83 With this option enabled the zcrypt device driver can
84 provide multiple devices nodes in /dev. Each device
85 node can get customized to limit access and narrow
86 down the use of the available crypto hardware.
89 tristate "Kernel API for protected key handling"
93 With this option enabled the pkey kernel module provides an API
94 for creation and handling of protected keys. Other parts of the
95 kernel or userspace applications may use these functions.
97 Select this option if you want to enable the kernel and userspace
98 API for proteced key handling.
100 Please note that creation of protected keys from secure keys
101 requires to have at least one CEX card in coprocessor mode
102 available at runtime.
104 config CRYPTO_PAES_S390
105 tristate "PAES cipher algorithms"
110 select CRYPTO_BLKCIPHER
112 This is the s390 hardware accelerated implementation of the
113 AES cipher algorithms for use with protected key.
115 Select this option if you want to use the paes cipher
116 for example to use protected key encrypted devices.
118 config CRYPTO_SHA1_S390
119 tristate "SHA1 digest algorithm"
123 This is the s390 hardware accelerated implementation of the
124 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
126 It is available as of z990.
128 config CRYPTO_SHA256_S390
129 tristate "SHA256 digest algorithm"
133 This is the s390 hardware accelerated implementation of the
134 SHA256 secure hash standard (DFIPS 180-2).
136 It is available as of z9.
138 config CRYPTO_SHA512_S390
139 tristate "SHA384 and SHA512 digest algorithm"
143 This is the s390 hardware accelerated implementation of the
144 SHA512 secure hash standard.
146 It is available as of z10.
148 config CRYPTO_SHA3_256_S390
149 tristate "SHA3_224 and SHA3_256 digest algorithm"
153 This is the s390 hardware accelerated implementation of the
154 SHA3_256 secure hash standard.
156 It is available as of z14.
158 config CRYPTO_SHA3_512_S390
159 tristate "SHA3_384 and SHA3_512 digest algorithm"
163 This is the s390 hardware accelerated implementation of the
164 SHA3_512 secure hash standard.
166 It is available as of z14.
168 config CRYPTO_DES_S390
169 tristate "DES and Triple DES cipher algorithms"
172 select CRYPTO_BLKCIPHER
173 select CRYPTO_LIB_DES
175 This is the s390 hardware accelerated implementation of the
176 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
178 As of z990 the ECB and CBC mode are hardware accelerated.
179 As of z196 the CTR mode is hardware accelerated.
181 config CRYPTO_AES_S390
182 tristate "AES cipher algorithms"
185 select CRYPTO_BLKCIPHER
187 This is the s390 hardware accelerated implementation of the
188 AES cipher algorithms (FIPS-197).
190 As of z9 the ECB and CBC modes are hardware accelerated
192 As of z10 the ECB and CBC modes are hardware accelerated
193 for all AES key sizes.
194 As of z196 the CTR mode is hardware accelerated for all AES
195 key sizes and XTS mode is hardware accelerated for 256 and
199 tristate "Pseudo random number generator device driver"
203 Select this option if you want to use the s390 pseudo random number
204 generator. The PRNG is part of the cryptographic processor functions
205 and uses triple-DES to generate secure random numbers like the
206 ANSI X9.17 standard. User-space programs access the
207 pseudo-random-number device through the char device /dev/prandom.
209 It is available as of z9.
211 config CRYPTO_GHASH_S390
212 tristate "GHASH hash function"
216 This is the s390 hardware accelerated implementation of GHASH,
217 the hash function used in GCM (Galois/Counter mode).
219 It is available as of z196.
221 config CRYPTO_CRC32_S390
222 tristate "CRC-32 algorithms"
227 Select this option if you want to use hardware accelerated
228 implementations of CRC algorithms. With this option, you
229 can optimize the computation of CRC-32 (IEEE 802.3 Ethernet)
230 and CRC-32C (Castagnoli).
232 It is available with IBM z13 or later.
234 config CRYPTO_DEV_MARVELL_CESA
235 tristate "Marvell's Cryptographic Engine driver"
236 depends on PLAT_ORION || ARCH_MVEBU
237 select CRYPTO_LIB_AES
238 select CRYPTO_LIB_DES
239 select CRYPTO_BLKCIPHER
243 This driver allows you to utilize the Cryptographic Engines and
244 Security Accelerator (CESA) which can be found on MVEBU and ORION
246 This driver supports CPU offload through DMA transfers.
248 config CRYPTO_DEV_NIAGARA2
249 tristate "Niagara2 Stream Processing Unit driver"
250 select CRYPTO_LIB_DES
251 select CRYPTO_BLKCIPHER
258 Each core of a Niagara2 processor contains a Stream
259 Processing Unit, which itself contains several cryptographic
260 sub-units. One set provides the Modular Arithmetic Unit,
261 used for SSL offload. The other set provides the Cipher
262 Group, which can perform encryption, decryption, hashing,
263 checksumming, and raw copies.
265 config CRYPTO_DEV_HIFN_795X
266 tristate "Driver HIFN 795x crypto accelerator chips"
267 select CRYPTO_LIB_DES
268 select CRYPTO_BLKCIPHER
269 select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG
271 depends on !ARCH_DMA_ADDR_T_64BIT
273 This option allows you to have support for HIFN 795x crypto adapters.
275 config CRYPTO_DEV_HIFN_795X_RNG
276 bool "HIFN 795x random number generator"
277 depends on CRYPTO_DEV_HIFN_795X
279 Select this option if you want to enable the random number generator
280 on the HIFN 795x crypto adapters.
282 source "drivers/crypto/caam/Kconfig"
284 config CRYPTO_DEV_TALITOS
285 tristate "Talitos Freescale Security Engine (SEC)"
287 select CRYPTO_AUTHENC
288 select CRYPTO_BLKCIPHER
293 Say 'Y' here to use the Freescale Security Engine (SEC)
294 to offload cryptographic algorithm computation.
296 The Freescale SEC is present on PowerQUICC 'E' processors, such
297 as the MPC8349E and MPC8548E.
299 To compile this driver as a module, choose M here: the module
300 will be called talitos.
302 config CRYPTO_DEV_TALITOS1
303 bool "SEC1 (SEC 1.0 and SEC Lite 1.2)"
304 depends on CRYPTO_DEV_TALITOS
305 depends on PPC_8xx || PPC_82xx
308 Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0
309 found on MPC82xx or the Freescale Security Engine (SEC Lite)
310 version 1.2 found on MPC8xx
312 config CRYPTO_DEV_TALITOS2
313 bool "SEC2+ (SEC version 2.0 or upper)"
314 depends on CRYPTO_DEV_TALITOS
315 default y if !PPC_8xx
317 Say 'Y' here to use the Freescale Security Engine (SEC)
318 version 2 and following as found on MPC83xx, MPC85xx, etc ...
320 config CRYPTO_DEV_IXP4XX
321 tristate "Driver for IXP4xx crypto hardware acceleration"
322 depends on ARCH_IXP4XX && IXP4XX_QMGR && IXP4XX_NPE
323 select CRYPTO_LIB_DES
325 select CRYPTO_AUTHENC
326 select CRYPTO_BLKCIPHER
328 Driver for the IXP4xx NPE crypto engine.
330 config CRYPTO_DEV_PPC4XX
331 tristate "Driver AMCC PPC4xx crypto accelerator"
332 depends on PPC && 4xx
335 select CRYPTO_LIB_AES
339 select CRYPTO_BLKCIPHER
341 This option allows you to have support for AMCC crypto acceleration.
343 config HW_RANDOM_PPC4XX
344 bool "PowerPC 4xx generic true random number generator support"
345 depends on CRYPTO_DEV_PPC4XX && HW_RANDOM
348 This option provides the kernel-side support for the TRNG hardware
349 found in the security function of some PowerPC 4xx SoCs.
351 config CRYPTO_DEV_OMAP
352 tristate "Support for OMAP crypto HW accelerators"
353 depends on ARCH_OMAP2PLUS
355 OMAP processors have various crypto HW accelerators. Select this if
356 you want to use the OMAP modules for any of the crypto algorithms.
360 config CRYPTO_DEV_OMAP_SHAM
361 tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator"
362 depends on ARCH_OMAP2PLUS
369 OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you
370 want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
372 config CRYPTO_DEV_OMAP_AES
373 tristate "Support for OMAP AES hw engine"
374 depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS
376 select CRYPTO_BLKCIPHER
383 OMAP processors have AES module accelerator. Select this if you
384 want to use the OMAP module for AES algorithms.
386 config CRYPTO_DEV_OMAP_DES
387 tristate "Support for OMAP DES/3DES hw engine"
388 depends on ARCH_OMAP2PLUS
389 select CRYPTO_LIB_DES
390 select CRYPTO_BLKCIPHER
393 OMAP processors have DES/3DES module accelerator. Select this if you
394 want to use the OMAP module for DES and 3DES algorithms. Currently
395 the ECB and CBC modes of operation are supported by the driver. Also
396 accesses made on unaligned boundaries are supported.
398 endif # CRYPTO_DEV_OMAP
400 config CRYPTO_DEV_PICOXCELL
401 tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
402 depends on (ARCH_PICOXCELL || COMPILE_TEST) && HAVE_CLK
405 select CRYPTO_AUTHENC
406 select CRYPTO_BLKCIPHER
407 select CRYPTO_LIB_DES
412 This option enables support for the hardware offload engines in the
413 Picochip picoXcell SoC devices. Select this for IPSEC ESP offload
414 and for 3gpp Layer 2 ciphering support.
416 Saying m here will build a module named picoxcell_crypto.
418 config CRYPTO_DEV_SAHARA
419 tristate "Support for SAHARA crypto accelerator"
420 depends on ARCH_MXC && OF
421 select CRYPTO_BLKCIPHER
425 This option enables support for the SAHARA HW crypto accelerator
426 found in some Freescale i.MX chips.
428 config CRYPTO_DEV_EXYNOS_RNG
429 tristate "EXYNOS HW pseudo random number generator support"
430 depends on ARCH_EXYNOS || COMPILE_TEST
434 This driver provides kernel-side support through the
435 cryptographic API for the pseudo random number generator hardware
436 found on Exynos SoCs.
438 To compile this driver as a module, choose M here: the
439 module will be called exynos-rng.
443 config CRYPTO_DEV_S5P
444 tristate "Support for Samsung S5PV210/Exynos crypto accelerator"
445 depends on ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST
448 select CRYPTO_BLKCIPHER
450 This option allows you to have support for S5P crypto acceleration.
451 Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES
452 algorithms execution.
454 config CRYPTO_DEV_EXYNOS_HASH
455 bool "Support for Samsung Exynos HASH accelerator"
456 depends on CRYPTO_DEV_S5P
457 depends on !CRYPTO_DEV_EXYNOS_RNG && CRYPTO_DEV_EXYNOS_RNG!=m
462 Select this to offload Exynos from HASH MD5/SHA1/SHA256.
463 This will select software SHA1, MD5 and SHA256 as they are
464 needed for small and zero-size messages.
465 HASH algorithms will be disabled if EXYNOS_RNG
466 is enabled due to hw conflict.
469 bool "Support for IBM PowerPC Nest (NX) cryptographic acceleration"
472 This enables support for the NX hardware cryptographic accelerator
473 coprocessor that is in IBM PowerPC P7+ or later processors. This
474 does not actually enable any drivers, it only allows you to select
475 which acceleration type (encryption and/or compression) to enable.
478 source "drivers/crypto/nx/Kconfig"
481 config CRYPTO_DEV_UX500
482 tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration"
483 depends on ARCH_U8500
485 Driver for ST-Ericsson UX500 crypto engine.
488 source "drivers/crypto/ux500/Kconfig"
489 endif # if CRYPTO_DEV_UX500
491 config CRYPTO_DEV_ATMEL_AUTHENC
492 tristate "Support for Atmel IPSEC/SSL hw accelerator"
493 depends on ARCH_AT91 || COMPILE_TEST
494 select CRYPTO_AUTHENC
495 select CRYPTO_DEV_ATMEL_AES
496 select CRYPTO_DEV_ATMEL_SHA
498 Some Atmel processors can combine the AES and SHA hw accelerators
499 to enhance support of IPSEC/SSL.
500 Select this if you want to use the Atmel modules for
501 authenc(hmac(shaX),Y(cbc)) algorithms.
503 config CRYPTO_DEV_ATMEL_AES
504 tristate "Support for Atmel AES hw accelerator"
505 depends on ARCH_AT91 || COMPILE_TEST
508 select CRYPTO_BLKCIPHER
510 Some Atmel processors have AES hw accelerator.
511 Select this if you want to use the Atmel module for
514 To compile this driver as a module, choose M here: the module
515 will be called atmel-aes.
517 config CRYPTO_DEV_ATMEL_TDES
518 tristate "Support for Atmel DES/TDES hw accelerator"
519 depends on ARCH_AT91 || COMPILE_TEST
520 select CRYPTO_LIB_DES
521 select CRYPTO_BLKCIPHER
523 Some Atmel processors have DES/TDES hw accelerator.
524 Select this if you want to use the Atmel module for
527 To compile this driver as a module, choose M here: the module
528 will be called atmel-tdes.
530 config CRYPTO_DEV_ATMEL_SHA
531 tristate "Support for Atmel SHA hw accelerator"
532 depends on ARCH_AT91 || COMPILE_TEST
535 Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
537 Select this if you want to use the Atmel module for
538 SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
540 To compile this driver as a module, choose M here: the module
541 will be called atmel-sha.
543 config CRYPTO_DEV_ATMEL_I2C
546 config CRYPTO_DEV_ATMEL_ECC
547 tristate "Support for Microchip / Atmel ECC hw accelerator"
549 select CRYPTO_DEV_ATMEL_I2C
553 Microhip / Atmel ECC hw accelerator.
554 Select this if you want to use the Microchip / Atmel module for
557 To compile this driver as a module, choose M here: the module
558 will be called atmel-ecc.
560 config CRYPTO_DEV_ATMEL_SHA204A
561 tristate "Support for Microchip / Atmel SHA accelerator and RNG"
563 select CRYPTO_DEV_ATMEL_I2C
567 Microhip / Atmel SHA accelerator and RNG.
568 Select this if you want to use the Microchip / Atmel SHA204A
569 module as a random number generator. (Other functions of the
570 chip are currently not exposed by this driver)
572 To compile this driver as a module, choose M here: the module
573 will be called atmel-sha204a.
575 config CRYPTO_DEV_CCP
576 bool "Support for AMD Secure Processor"
577 depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM
579 The AMD Secure Processor provides support for the Cryptographic Coprocessor
580 (CCP) and the Platform Security Processor (PSP) devices.
583 source "drivers/crypto/ccp/Kconfig"
586 config CRYPTO_DEV_MXS_DCP
587 tristate "Support for Freescale MXS DCP"
588 depends on (ARCH_MXS || ARCH_MXC)
593 select CRYPTO_BLKCIPHER
596 The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB
597 co-processor on the die.
599 To compile this driver as a module, choose M here: the module
600 will be called mxs-dcp.
602 source "drivers/crypto/qat/Kconfig"
603 source "drivers/crypto/cavium/cpt/Kconfig"
604 source "drivers/crypto/cavium/nitrox/Kconfig"
606 config CRYPTO_DEV_CAVIUM_ZIP
607 tristate "Cavium ZIP driver"
608 depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
610 Select this option if you want to enable compression/decompression
611 acceleration on Cavium's ARM based SoCs
613 config CRYPTO_DEV_QCE
614 tristate "Qualcomm crypto engine accelerator"
615 depends on ARCH_QCOM || COMPILE_TEST
618 select CRYPTO_LIB_DES
623 select CRYPTO_BLKCIPHER
625 This driver supports Qualcomm crypto engine accelerator
626 hardware. To compile this driver as a module, choose M here. The
627 module will be called qcrypto.
629 config CRYPTO_DEV_QCOM_RNG
630 tristate "Qualcomm Random Number Generator Driver"
631 depends on ARCH_QCOM || COMPILE_TEST
634 This driver provides support for the Random Number
635 Generator hardware found on Qualcomm SoCs.
637 To compile this driver as a module, choose M here. The
638 module will be called qcom-rng. If unsure, say N.
640 config CRYPTO_DEV_VMX
641 bool "Support for VMX cryptographic acceleration instructions"
642 depends on PPC64 && VSX
644 Support for VMX cryptographic acceleration instructions.
646 source "drivers/crypto/vmx/Kconfig"
648 config CRYPTO_DEV_IMGTEC_HASH
649 tristate "Imagination Technologies hardware hash accelerator"
650 depends on MIPS || COMPILE_TEST
656 This driver interfaces with the Imagination Technologies
657 hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256
660 config CRYPTO_DEV_SUN4I_SS
661 tristate "Support for Allwinner Security System cryptographic accelerator"
662 depends on ARCH_SUNXI && !64BIT
666 select CRYPTO_LIB_DES
667 select CRYPTO_BLKCIPHER
669 Some Allwinner SoC have a crypto accelerator named
670 Security System. Select this if you want to use it.
671 The Security System handle AES/DES/3DES ciphers in CBC mode
672 and SHA1 and MD5 hash algorithms.
674 To compile this driver as a module, choose M here: the module
675 will be called sun4i-ss.
677 config CRYPTO_DEV_SUN4I_SS_PRNG
678 bool "Support for Allwinner Security System PRNG"
679 depends on CRYPTO_DEV_SUN4I_SS
682 Select this option if you want to provide kernel-side support for
683 the Pseudo-Random Number Generator found in the Security System.
685 config CRYPTO_DEV_ROCKCHIP
686 tristate "Rockchip's Cryptographic Engine driver"
687 depends on OF && ARCH_ROCKCHIP
689 select CRYPTO_LIB_DES
694 select CRYPTO_BLKCIPHER
697 This driver interfaces with the hardware crypto accelerator.
698 Supporting cbc/ecb chainmode, and aes/des/des3_ede cipher mode.
700 config CRYPTO_DEV_MEDIATEK
701 tristate "MediaTek's EIP97 Cryptographic Engine driver"
702 depends on (ARM && ARCH_MEDIATEK) || COMPILE_TEST
705 select CRYPTO_BLKCIPHER
712 This driver allows you to utilize the hardware crypto accelerator
713 EIP97 which can be found on the MT7623 MT2701, MT8521p, etc ....
714 Select this if you want to use it for AES/SHA1/SHA2 algorithms.
716 source "drivers/crypto/chelsio/Kconfig"
718 source "drivers/crypto/virtio/Kconfig"
720 config CRYPTO_DEV_BCM_SPU
721 tristate "Broadcom symmetric crypto/hash acceleration support"
722 depends on ARCH_BCM_IPROC
725 select CRYPTO_AUTHENC
726 select CRYPTO_LIB_DES
732 This driver provides support for Broadcom crypto acceleration using the
733 Secure Processing Unit (SPU). The SPU driver registers ablkcipher,
734 ahash, and aead algorithms with the kernel cryptographic API.
736 source "drivers/crypto/stm32/Kconfig"
738 config CRYPTO_DEV_SAFEXCEL
739 tristate "Inside Secure's SafeXcel cryptographic engine driver"
740 depends on OF || PCI || COMPILE_TEST
741 select CRYPTO_LIB_AES
742 select CRYPTO_AUTHENC
743 select CRYPTO_BLKCIPHER
744 select CRYPTO_LIB_DES
752 This driver interfaces with the SafeXcel EIP-97 and EIP-197 cryptographic
753 engines designed by Inside Secure. It currently accelerates DES, 3DES and
754 AES block ciphers in ECB and CBC mode, as well as SHA1, SHA224, SHA256,
755 SHA384 and SHA512 hash algorithms for both basic hash and HMAC.
756 Additionally, it accelerates combined AES-CBC/HMAC-SHA AEAD operations.
758 config CRYPTO_DEV_ARTPEC6
759 tristate "Support for Axis ARTPEC-6/7 hardware crypto acceleration."
760 depends on ARM && (ARCH_ARTPEC || COMPILE_TEST)
765 select CRYPTO_BLKCIPHER
772 Enables the driver for the on-chip crypto accelerator
775 To compile this driver as a module, choose M here.
777 config CRYPTO_DEV_CCREE
778 tristate "Support for ARM TrustZone CryptoCell family of security processors"
779 depends on CRYPTO && CRYPTO_HW && OF && HAS_DMA
782 select CRYPTO_BLKCIPHER
783 select CRYPTO_LIB_DES
785 select CRYPTO_AUTHENC
799 Say 'Y' to enable a driver for the REE interface of the Arm
800 TrustZone CryptoCell family of processors. Currently the
801 CryptoCell 713, 703, 712, 710 and 630 are supported.
802 Choose this if you wish to use hardware acceleration of
803 cryptographic operations on the system REE.
806 source "drivers/crypto/hisilicon/Kconfig"