3 bool "Hardware crypto devices"
6 Say Y here to get to see options for hardware crypto devices and
7 processors. This option alone does not add any kernel code.
9 If you say N, all options in this submenu will be skipped and disabled.
13 config CRYPTO_DEV_PADLOCK
14 tristate "Support for VIA PadLock ACE"
15 depends on X86 && !UML
17 Some VIA processors come with an integrated crypto engine
18 (so called VIA PadLock ACE, Advanced Cryptography Engine)
19 that provides instructions for very fast cryptographic
20 operations with supported algorithms.
22 The instructions are used only when the CPU supports them.
23 Otherwise software encryption is used.
25 config CRYPTO_DEV_PADLOCK_AES
26 tristate "PadLock driver for AES algorithm"
27 depends on CRYPTO_DEV_PADLOCK
28 select CRYPTO_BLKCIPHER
31 Use VIA PadLock for AES algorithm.
33 Available in VIA C3 and newer CPUs.
35 If unsure say M. The compiled module will be
38 config CRYPTO_DEV_PADLOCK_SHA
39 tristate "PadLock driver for SHA1 and SHA256 algorithms"
40 depends on CRYPTO_DEV_PADLOCK
45 Use VIA PadLock for SHA1/SHA256 algorithms.
47 Available in VIA C7 and newer processors.
49 If unsure say M. The compiled module will be
52 config CRYPTO_DEV_GEODE
53 tristate "Support for the Geode LX AES engine"
54 depends on X86_32 && PCI
56 select CRYPTO_BLKCIPHER
58 Say 'Y' here to use the AMD Geode LX processor on-board AES
59 engine for the CryptoAPI AES algorithm.
61 To compile this driver as a module, choose M here: the module
62 will be called geode-aes.
65 tristate "Support for s390 cryptographic adapters"
69 Select this option if you want to enable support for
70 s390 cryptographic adapters like:
71 + PCI-X Cryptographic Coprocessor (PCIXCC)
72 + Crypto Express 2,3,4 or 5 Coprocessor (CEXxC)
73 + Crypto Express 2,3,4 or 5 Accelerator (CEXxA)
74 + Crypto Express 4 or 5 EP11 Coprocessor (CEXxP)
76 config ZCRYPT_MULTIDEVNODES
77 bool "Support for multiple zcrypt device nodes"
82 With this option enabled the zcrypt device driver can
83 provide multiple devices nodes in /dev. Each device
84 node can get customized to limit access and narrow
85 down the use of the available crypto hardware.
88 tristate "Kernel API for protected key handling"
92 With this option enabled the pkey kernel module provides an API
93 for creation and handling of protected keys. Other parts of the
94 kernel or userspace applications may use these functions.
96 Select this option if you want to enable the kernel and userspace
97 API for proteced key handling.
99 Please note that creation of protected keys from secure keys
100 requires to have at least one CEX card in coprocessor mode
101 available at runtime.
103 config CRYPTO_PAES_S390
104 tristate "PAES cipher algorithms"
109 select CRYPTO_BLKCIPHER
111 This is the s390 hardware accelerated implementation of the
112 AES cipher algorithms for use with protected key.
114 Select this option if you want to use the paes cipher
115 for example to use protected key encrypted devices.
117 config CRYPTO_SHA1_S390
118 tristate "SHA1 digest algorithm"
122 This is the s390 hardware accelerated implementation of the
123 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
125 It is available as of z990.
127 config CRYPTO_SHA256_S390
128 tristate "SHA256 digest algorithm"
132 This is the s390 hardware accelerated implementation of the
133 SHA256 secure hash standard (DFIPS 180-2).
135 It is available as of z9.
137 config CRYPTO_SHA512_S390
138 tristate "SHA384 and SHA512 digest algorithm"
142 This is the s390 hardware accelerated implementation of the
143 SHA512 secure hash standard.
145 It is available as of z10.
147 config CRYPTO_DES_S390
148 tristate "DES and Triple DES cipher algorithms"
151 select CRYPTO_BLKCIPHER
154 This is the s390 hardware accelerated implementation of the
155 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
157 As of z990 the ECB and CBC mode are hardware accelerated.
158 As of z196 the CTR mode is hardware accelerated.
160 config CRYPTO_AES_S390
161 tristate "AES cipher algorithms"
164 select CRYPTO_BLKCIPHER
166 This is the s390 hardware accelerated implementation of the
167 AES cipher algorithms (FIPS-197).
169 As of z9 the ECB and CBC modes are hardware accelerated
171 As of z10 the ECB and CBC modes are hardware accelerated
172 for all AES key sizes.
173 As of z196 the CTR mode is hardware accelerated for all AES
174 key sizes and XTS mode is hardware accelerated for 256 and
178 tristate "Pseudo random number generator device driver"
182 Select this option if you want to use the s390 pseudo random number
183 generator. The PRNG is part of the cryptographic processor functions
184 and uses triple-DES to generate secure random numbers like the
185 ANSI X9.17 standard. User-space programs access the
186 pseudo-random-number device through the char device /dev/prandom.
188 It is available as of z9.
190 config CRYPTO_GHASH_S390
191 tristate "GHASH digest algorithm"
195 This is the s390 hardware accelerated implementation of the
196 GHASH message digest algorithm for GCM (Galois/Counter Mode).
198 It is available as of z196.
200 config CRYPTO_CRC32_S390
201 tristate "CRC-32 algorithms"
206 Select this option if you want to use hardware accelerated
207 implementations of CRC algorithms. With this option, you
208 can optimize the computation of CRC-32 (IEEE 802.3 Ethernet)
209 and CRC-32C (Castagnoli).
211 It is available with IBM z13 or later.
213 config CRYPTO_DEV_MARVELL_CESA
214 tristate "Marvell's Cryptographic Engine driver"
215 depends on PLAT_ORION || ARCH_MVEBU
218 select CRYPTO_BLKCIPHER
222 This driver allows you to utilize the Cryptographic Engines and
223 Security Accelerator (CESA) which can be found on MVEBU and ORION
225 This driver supports CPU offload through DMA transfers.
227 config CRYPTO_DEV_NIAGARA2
228 tristate "Niagara2 Stream Processing Unit driver"
230 select CRYPTO_BLKCIPHER
237 Each core of a Niagara2 processor contains a Stream
238 Processing Unit, which itself contains several cryptographic
239 sub-units. One set provides the Modular Arithmetic Unit,
240 used for SSL offload. The other set provides the Cipher
241 Group, which can perform encryption, decryption, hashing,
242 checksumming, and raw copies.
244 config CRYPTO_DEV_HIFN_795X
245 tristate "Driver HIFN 795x crypto accelerator chips"
247 select CRYPTO_BLKCIPHER
248 select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG
250 depends on !ARCH_DMA_ADDR_T_64BIT
252 This option allows you to have support for HIFN 795x crypto adapters.
254 config CRYPTO_DEV_HIFN_795X_RNG
255 bool "HIFN 795x random number generator"
256 depends on CRYPTO_DEV_HIFN_795X
258 Select this option if you want to enable the random number generator
259 on the HIFN 795x crypto adapters.
261 source "drivers/crypto/caam/Kconfig"
263 config CRYPTO_DEV_TALITOS
264 tristate "Talitos Freescale Security Engine (SEC)"
266 select CRYPTO_AUTHENC
267 select CRYPTO_BLKCIPHER
272 Say 'Y' here to use the Freescale Security Engine (SEC)
273 to offload cryptographic algorithm computation.
275 The Freescale SEC is present on PowerQUICC 'E' processors, such
276 as the MPC8349E and MPC8548E.
278 To compile this driver as a module, choose M here: the module
279 will be called talitos.
281 config CRYPTO_DEV_TALITOS1
282 bool "SEC1 (SEC 1.0 and SEC Lite 1.2)"
283 depends on CRYPTO_DEV_TALITOS
284 depends on PPC_8xx || PPC_82xx
287 Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0
288 found on MPC82xx or the Freescale Security Engine (SEC Lite)
289 version 1.2 found on MPC8xx
291 config CRYPTO_DEV_TALITOS2
292 bool "SEC2+ (SEC version 2.0 or upper)"
293 depends on CRYPTO_DEV_TALITOS
294 default y if !PPC_8xx
296 Say 'Y' here to use the Freescale Security Engine (SEC)
297 version 2 and following as found on MPC83xx, MPC85xx, etc ...
299 config CRYPTO_DEV_IXP4XX
300 tristate "Driver for IXP4xx crypto hardware acceleration"
301 depends on ARCH_IXP4XX && IXP4XX_QMGR && IXP4XX_NPE
304 select CRYPTO_AUTHENC
305 select CRYPTO_BLKCIPHER
307 Driver for the IXP4xx NPE crypto engine.
309 config CRYPTO_DEV_PPC4XX
310 tristate "Driver AMCC PPC4xx crypto accelerator"
311 depends on PPC && 4xx
318 select CRYPTO_BLKCIPHER
320 This option allows you to have support for AMCC crypto acceleration.
322 config HW_RANDOM_PPC4XX
323 bool "PowerPC 4xx generic true random number generator support"
324 depends on CRYPTO_DEV_PPC4XX && HW_RANDOM
327 This option provides the kernel-side support for the TRNG hardware
328 found in the security function of some PowerPC 4xx SoCs.
330 config CRYPTO_DEV_OMAP
331 tristate "Support for OMAP crypto HW accelerators"
332 depends on ARCH_OMAP2PLUS
334 OMAP processors have various crypto HW accelerators. Select this if
335 you want to use the OMAP modules for any of the crypto algorithms.
339 config CRYPTO_DEV_OMAP_SHAM
340 tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator"
341 depends on ARCH_OMAP2PLUS
348 OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you
349 want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
351 config CRYPTO_DEV_OMAP_AES
352 tristate "Support for OMAP AES hw engine"
353 depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS
355 select CRYPTO_BLKCIPHER
362 OMAP processors have AES module accelerator. Select this if you
363 want to use the OMAP module for AES algorithms.
365 config CRYPTO_DEV_OMAP_DES
366 tristate "Support for OMAP DES/3DES hw engine"
367 depends on ARCH_OMAP2PLUS
369 select CRYPTO_BLKCIPHER
372 OMAP processors have DES/3DES module accelerator. Select this if you
373 want to use the OMAP module for DES and 3DES algorithms. Currently
374 the ECB and CBC modes of operation are supported by the driver. Also
375 accesses made on unaligned boundaries are supported.
377 endif # CRYPTO_DEV_OMAP
379 config CRYPTO_DEV_PICOXCELL
380 tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
381 depends on (ARCH_PICOXCELL || COMPILE_TEST) && HAVE_CLK
384 select CRYPTO_AUTHENC
385 select CRYPTO_BLKCIPHER
391 This option enables support for the hardware offload engines in the
392 Picochip picoXcell SoC devices. Select this for IPSEC ESP offload
393 and for 3gpp Layer 2 ciphering support.
395 Saying m here will build a module named pipcoxcell_crypto.
397 config CRYPTO_DEV_SAHARA
398 tristate "Support for SAHARA crypto accelerator"
399 depends on ARCH_MXC && OF
400 select CRYPTO_BLKCIPHER
404 This option enables support for the SAHARA HW crypto accelerator
405 found in some Freescale i.MX chips.
407 config CRYPTO_DEV_EXYNOS_RNG
408 tristate "EXYNOS HW pseudo random number generator support"
409 depends on ARCH_EXYNOS || COMPILE_TEST
413 This driver provides kernel-side support through the
414 cryptographic API for the pseudo random number generator hardware
415 found on Exynos SoCs.
417 To compile this driver as a module, choose M here: the
418 module will be called exynos-rng.
422 config CRYPTO_DEV_S5P
423 tristate "Support for Samsung S5PV210/Exynos crypto accelerator"
424 depends on ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST
427 select CRYPTO_BLKCIPHER
429 This option allows you to have support for S5P crypto acceleration.
430 Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES
431 algorithms execution.
433 config CRYPTO_DEV_EXYNOS_HASH
434 bool "Support for Samsung Exynos HASH accelerator"
435 depends on CRYPTO_DEV_S5P
436 depends on !CRYPTO_DEV_EXYNOS_RNG && CRYPTO_DEV_EXYNOS_RNG!=m
441 Select this to offload Exynos from HASH MD5/SHA1/SHA256.
442 This will select software SHA1, MD5 and SHA256 as they are
443 needed for small and zero-size messages.
444 HASH algorithms will be disabled if EXYNOS_RNG
445 is enabled due to hw conflict.
448 bool "Support for IBM PowerPC Nest (NX) cryptographic acceleration"
451 This enables support for the NX hardware cryptographic accelerator
452 coprocessor that is in IBM PowerPC P7+ or later processors. This
453 does not actually enable any drivers, it only allows you to select
454 which acceleration type (encryption and/or compression) to enable.
457 source "drivers/crypto/nx/Kconfig"
460 config CRYPTO_DEV_UX500
461 tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration"
462 depends on ARCH_U8500
464 Driver for ST-Ericsson UX500 crypto engine.
467 source "drivers/crypto/ux500/Kconfig"
468 endif # if CRYPTO_DEV_UX500
470 config CRYPTO_DEV_ATMEL_AUTHENC
471 tristate "Support for Atmel IPSEC/SSL hw accelerator"
472 depends on ARCH_AT91 || COMPILE_TEST
473 select CRYPTO_AUTHENC
474 select CRYPTO_DEV_ATMEL_AES
475 select CRYPTO_DEV_ATMEL_SHA
477 Some Atmel processors can combine the AES and SHA hw accelerators
478 to enhance support of IPSEC/SSL.
479 Select this if you want to use the Atmel modules for
480 authenc(hmac(shaX),Y(cbc)) algorithms.
482 config CRYPTO_DEV_ATMEL_AES
483 tristate "Support for Atmel AES hw accelerator"
484 depends on ARCH_AT91 || COMPILE_TEST
487 select CRYPTO_BLKCIPHER
489 Some Atmel processors have AES hw accelerator.
490 Select this if you want to use the Atmel module for
493 To compile this driver as a module, choose M here: the module
494 will be called atmel-aes.
496 config CRYPTO_DEV_ATMEL_TDES
497 tristate "Support for Atmel DES/TDES hw accelerator"
498 depends on ARCH_AT91 || COMPILE_TEST
500 select CRYPTO_BLKCIPHER
502 Some Atmel processors have DES/TDES hw accelerator.
503 Select this if you want to use the Atmel module for
506 To compile this driver as a module, choose M here: the module
507 will be called atmel-tdes.
509 config CRYPTO_DEV_ATMEL_SHA
510 tristate "Support for Atmel SHA hw accelerator"
511 depends on ARCH_AT91 || COMPILE_TEST
514 Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
516 Select this if you want to use the Atmel module for
517 SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
519 To compile this driver as a module, choose M here: the module
520 will be called atmel-sha.
522 config CRYPTO_DEV_ATMEL_ECC
523 tristate "Support for Microchip / Atmel ECC hw accelerator"
524 depends on ARCH_AT91 || COMPILE_TEST
529 Microhip / Atmel ECC hw accelerator.
530 Select this if you want to use the Microchip / Atmel module for
533 To compile this driver as a module, choose M here: the module
534 will be called atmel-ecc.
536 config CRYPTO_DEV_CCP
537 bool "Support for AMD Secure Processor"
538 depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM
540 The AMD Secure Processor provides support for the Cryptographic Coprocessor
541 (CCP) and the Platform Security Processor (PSP) devices.
544 source "drivers/crypto/ccp/Kconfig"
547 config CRYPTO_DEV_MXS_DCP
548 tristate "Support for Freescale MXS DCP"
549 depends on (ARCH_MXS || ARCH_MXC)
554 select CRYPTO_BLKCIPHER
557 The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB
558 co-processor on the die.
560 To compile this driver as a module, choose M here: the module
561 will be called mxs-dcp.
563 source "drivers/crypto/qat/Kconfig"
564 source "drivers/crypto/cavium/cpt/Kconfig"
565 source "drivers/crypto/cavium/nitrox/Kconfig"
567 config CRYPTO_DEV_CAVIUM_ZIP
568 tristate "Cavium ZIP driver"
569 depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
571 Select this option if you want to enable compression/decompression
572 acceleration on Cavium's ARM based SoCs
574 config CRYPTO_DEV_QCE
575 tristate "Qualcomm crypto engine accelerator"
576 depends on ARCH_QCOM || COMPILE_TEST
584 select CRYPTO_BLKCIPHER
586 This driver supports Qualcomm crypto engine accelerator
587 hardware. To compile this driver as a module, choose M here. The
588 module will be called qcrypto.
590 config CRYPTO_DEV_QCOM_RNG
591 tristate "Qualcomm Random Number Generator Driver"
592 depends on ARCH_QCOM || COMPILE_TEST
595 This driver provides support for the Random Number
596 Generator hardware found on Qualcomm SoCs.
598 To compile this driver as a module, choose M here. The
599 module will be called qcom-rng. If unsure, say N.
601 config CRYPTO_DEV_VMX
602 bool "Support for VMX cryptographic acceleration instructions"
603 depends on PPC64 && VSX
605 Support for VMX cryptographic acceleration instructions.
607 source "drivers/crypto/vmx/Kconfig"
609 config CRYPTO_DEV_IMGTEC_HASH
610 tristate "Imagination Technologies hardware hash accelerator"
611 depends on MIPS || COMPILE_TEST
617 This driver interfaces with the Imagination Technologies
618 hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256
621 config CRYPTO_DEV_SUN4I_SS
622 tristate "Support for Allwinner Security System cryptographic accelerator"
623 depends on ARCH_SUNXI && !64BIT
628 select CRYPTO_BLKCIPHER
630 Some Allwinner SoC have a crypto accelerator named
631 Security System. Select this if you want to use it.
632 The Security System handle AES/DES/3DES ciphers in CBC mode
633 and SHA1 and MD5 hash algorithms.
635 To compile this driver as a module, choose M here: the module
636 will be called sun4i-ss.
638 config CRYPTO_DEV_SUN4I_SS_PRNG
639 bool "Support for Allwinner Security System PRNG"
640 depends on CRYPTO_DEV_SUN4I_SS
643 Select this option if you want to provide kernel-side support for
644 the Pseudo-Random Number Generator found in the Security System.
646 config CRYPTO_DEV_ROCKCHIP
647 tristate "Rockchip's Cryptographic Engine driver"
648 depends on OF && ARCH_ROCKCHIP
655 select CRYPTO_BLKCIPHER
658 This driver interfaces with the hardware crypto accelerator.
659 Supporting cbc/ecb chainmode, and aes/des/des3_ede cipher mode.
661 config CRYPTO_DEV_MEDIATEK
662 tristate "MediaTek's EIP97 Cryptographic Engine driver"
663 depends on (ARM && ARCH_MEDIATEK) || COMPILE_TEST
666 select CRYPTO_BLKCIPHER
673 This driver allows you to utilize the hardware crypto accelerator
674 EIP97 which can be found on the MT7623 MT2701, MT8521p, etc ....
675 Select this if you want to use it for AES/SHA1/SHA2 algorithms.
677 source "drivers/crypto/chelsio/Kconfig"
679 source "drivers/crypto/virtio/Kconfig"
681 config CRYPTO_DEV_BCM_SPU
682 tristate "Broadcom symmetric crypto/hash acceleration support"
683 depends on ARCH_BCM_IPROC
686 select CRYPTO_AUTHENC
693 This driver provides support for Broadcom crypto acceleration using the
694 Secure Processing Unit (SPU). The SPU driver registers ablkcipher,
695 ahash, and aead algorithms with the kernel cryptographic API.
697 source "drivers/crypto/stm32/Kconfig"
699 config CRYPTO_DEV_SAFEXCEL
700 tristate "Inside Secure's SafeXcel cryptographic engine driver"
702 depends on (ARM64 && ARCH_MVEBU) || (COMPILE_TEST && 64BIT)
704 select CRYPTO_AUTHENC
705 select CRYPTO_BLKCIPHER
714 This driver interfaces with the SafeXcel EIP-197 cryptographic engine
715 designed by Inside Secure. Select this if you want to use CBC/ECB
716 chain mode, AES cipher mode and SHA1/SHA224/SHA256/SHA512 hash
719 config CRYPTO_DEV_ARTPEC6
720 tristate "Support for Axis ARTPEC-6/7 hardware crypto acceleration."
721 depends on ARM && (ARCH_ARTPEC || COMPILE_TEST)
726 select CRYPTO_BLKCIPHER
733 Enables the driver for the on-chip crypto accelerator
736 To compile this driver as a module, choose M here.
738 config CRYPTO_DEV_CCREE
739 tristate "Support for ARM TrustZone CryptoCell family of security processors"
740 depends on CRYPTO && CRYPTO_HW && OF && HAS_DMA
743 select CRYPTO_BLKCIPHER
746 select CRYPTO_AUTHENC
760 Say 'Y' to enable a driver for the REE interface of the Arm
761 TrustZone CryptoCell family of processors. Currently the
762 CryptoCell 713, 703, 712, 710 and 630 are supported.
763 Choose this if you wish to use hardware acceleration of
764 cryptographic operations on the system REE.
767 source "drivers/crypto/hisilicon/Kconfig"