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 source "drivers/crypto/allwinner/Kconfig"
16 config CRYPTO_DEV_PADLOCK
17 tristate "Support for VIA PadLock ACE"
18 depends on X86 && !UML
20 Some VIA processors come with an integrated crypto engine
21 (so called VIA PadLock ACE, Advanced Cryptography Engine)
22 that provides instructions for very fast cryptographic
23 operations with supported algorithms.
25 The instructions are used only when the CPU supports them.
26 Otherwise software encryption is used.
28 config CRYPTO_DEV_PADLOCK_AES
29 tristate "PadLock driver for AES algorithm"
30 depends on CRYPTO_DEV_PADLOCK
31 select CRYPTO_SKCIPHER
34 Use VIA PadLock for AES algorithm.
36 Available in VIA C3 and newer CPUs.
38 If unsure say M. The compiled module will be
41 config CRYPTO_DEV_PADLOCK_SHA
42 tristate "PadLock driver for SHA1 and SHA256 algorithms"
43 depends on CRYPTO_DEV_PADLOCK
48 Use VIA PadLock for SHA1/SHA256 algorithms.
50 Available in VIA C7 and newer processors.
52 If unsure say M. The compiled module will be
55 config CRYPTO_DEV_GEODE
56 tristate "Support for the Geode LX AES engine"
57 depends on X86_32 && PCI
59 select CRYPTO_SKCIPHER
61 Say 'Y' here to use the AMD Geode LX processor on-board AES
62 engine for the CryptoAPI AES algorithm.
64 To compile this driver as a module, choose M here: the module
65 will be called geode-aes.
68 tristate "Support for s390 cryptographic adapters"
72 Select this option if you want to enable support for
73 s390 cryptographic adapters like:
74 + Crypto Express 2 up to 7 Coprocessor (CEXxC)
75 + Crypto Express 2 up to 7 Accelerator (CEXxA)
76 + Crypto Express 4 up to 7 EP11 Coprocessor (CEXxP)
79 bool "Enable debug features for s390 cryptographic adapters"
81 depends on DEBUG_KERNEL
84 Say 'Y' here to enable some additional debug features on the
85 s390 cryptographic adapters driver.
87 There will be some more sysfs attributes displayed for ap cards
88 and queues and some flags on crypto requests are interpreted as
89 debugging messages to force error injection.
91 Do not enable on production level kernel build.
95 config ZCRYPT_MULTIDEVNODES
96 bool "Support for multiple zcrypt device nodes"
101 With this option enabled the zcrypt device driver can
102 provide multiple devices nodes in /dev. Each device
103 node can get customized to limit access and narrow
104 down the use of the available crypto hardware.
107 tristate "Kernel API for protected key handling"
111 With this option enabled the pkey kernel module provides an API
112 for creation and handling of protected keys. Other parts of the
113 kernel or userspace applications may use these functions.
115 Select this option if you want to enable the kernel and userspace
116 API for proteced key handling.
118 Please note that creation of protected keys from secure keys
119 requires to have at least one CEX card in coprocessor mode
120 available at runtime.
122 config CRYPTO_PAES_S390
123 tristate "PAES cipher algorithms"
128 select CRYPTO_SKCIPHER
130 This is the s390 hardware accelerated implementation of the
131 AES cipher algorithms for use with protected key.
133 Select this option if you want to use the paes cipher
134 for example to use protected key encrypted devices.
136 config CRYPTO_SHA1_S390
137 tristate "SHA1 digest algorithm"
141 This is the s390 hardware accelerated implementation of the
142 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
144 It is available as of z990.
146 config CRYPTO_SHA256_S390
147 tristate "SHA256 digest algorithm"
151 This is the s390 hardware accelerated implementation of the
152 SHA256 secure hash standard (DFIPS 180-2).
154 It is available as of z9.
156 config CRYPTO_SHA512_S390
157 tristate "SHA384 and SHA512 digest algorithm"
161 This is the s390 hardware accelerated implementation of the
162 SHA512 secure hash standard.
164 It is available as of z10.
166 config CRYPTO_SHA3_256_S390
167 tristate "SHA3_224 and SHA3_256 digest algorithm"
171 This is the s390 hardware accelerated implementation of the
172 SHA3_256 secure hash standard.
174 It is available as of z14.
176 config CRYPTO_SHA3_512_S390
177 tristate "SHA3_384 and SHA3_512 digest algorithm"
181 This is the s390 hardware accelerated implementation of the
182 SHA3_512 secure hash standard.
184 It is available as of z14.
186 config CRYPTO_DES_S390
187 tristate "DES and Triple DES cipher algorithms"
190 select CRYPTO_SKCIPHER
191 select CRYPTO_LIB_DES
193 This is the s390 hardware accelerated implementation of the
194 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
196 As of z990 the ECB and CBC mode are hardware accelerated.
197 As of z196 the CTR mode is hardware accelerated.
199 config CRYPTO_AES_S390
200 tristate "AES cipher algorithms"
203 select CRYPTO_SKCIPHER
205 This is the s390 hardware accelerated implementation of the
206 AES cipher algorithms (FIPS-197).
208 As of z9 the ECB and CBC modes are hardware accelerated
210 As of z10 the ECB and CBC modes are hardware accelerated
211 for all AES key sizes.
212 As of z196 the CTR mode is hardware accelerated for all AES
213 key sizes and XTS mode is hardware accelerated for 256 and
217 tristate "Pseudo random number generator device driver"
221 Select this option if you want to use the s390 pseudo random number
222 generator. The PRNG is part of the cryptographic processor functions
223 and uses triple-DES to generate secure random numbers like the
224 ANSI X9.17 standard. User-space programs access the
225 pseudo-random-number device through the char device /dev/prandom.
227 It is available as of z9.
229 config CRYPTO_GHASH_S390
230 tristate "GHASH hash function"
234 This is the s390 hardware accelerated implementation of GHASH,
235 the hash function used in GCM (Galois/Counter mode).
237 It is available as of z196.
239 config CRYPTO_CRC32_S390
240 tristate "CRC-32 algorithms"
245 Select this option if you want to use hardware accelerated
246 implementations of CRC algorithms. With this option, you
247 can optimize the computation of CRC-32 (IEEE 802.3 Ethernet)
248 and CRC-32C (Castagnoli).
250 It is available with IBM z13 or later.
252 config CRYPTO_DEV_NIAGARA2
253 tristate "Niagara2 Stream Processing Unit driver"
254 select CRYPTO_LIB_DES
255 select CRYPTO_SKCIPHER
262 Each core of a Niagara2 processor contains a Stream
263 Processing Unit, which itself contains several cryptographic
264 sub-units. One set provides the Modular Arithmetic Unit,
265 used for SSL offload. The other set provides the Cipher
266 Group, which can perform encryption, decryption, hashing,
267 checksumming, and raw copies.
269 config CRYPTO_DEV_SL3516
270 tristate "Stormlink SL3516 crypto offloader"
271 select CRYPTO_SKCIPHER
278 This option allows you to have support for SL3516 crypto offloader.
280 config CRYPTO_DEV_SL3516_DEBUG
281 bool "Enable SL3516 stats"
282 depends on CRYPTO_DEV_SL3516
285 Say y to enable SL3516 debug stats.
286 This will create /sys/kernel/debug/sl3516/stats for displaying
287 the number of requests per algorithm and other internal stats.
289 config CRYPTO_DEV_HIFN_795X
290 tristate "Driver HIFN 795x crypto accelerator chips"
291 select CRYPTO_LIB_DES
292 select CRYPTO_SKCIPHER
293 select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG
295 depends on !ARCH_DMA_ADDR_T_64BIT
297 This option allows you to have support for HIFN 795x crypto adapters.
299 config CRYPTO_DEV_HIFN_795X_RNG
300 bool "HIFN 795x random number generator"
301 depends on CRYPTO_DEV_HIFN_795X
303 Select this option if you want to enable the random number generator
304 on the HIFN 795x crypto adapters.
306 source "drivers/crypto/caam/Kconfig"
308 config CRYPTO_DEV_TALITOS
309 tristate "Talitos Freescale Security Engine (SEC)"
311 select CRYPTO_AUTHENC
312 select CRYPTO_SKCIPHER
314 select CRYPTO_LIB_DES
318 Say 'Y' here to use the Freescale Security Engine (SEC)
319 to offload cryptographic algorithm computation.
321 The Freescale SEC is present on PowerQUICC 'E' processors, such
322 as the MPC8349E and MPC8548E.
324 To compile this driver as a module, choose M here: the module
325 will be called talitos.
327 config CRYPTO_DEV_TALITOS1
328 bool "SEC1 (SEC 1.0 and SEC Lite 1.2)"
329 depends on CRYPTO_DEV_TALITOS
330 depends on PPC_8xx || PPC_82xx
333 Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0
334 found on MPC82xx or the Freescale Security Engine (SEC Lite)
335 version 1.2 found on MPC8xx
337 config CRYPTO_DEV_TALITOS2
338 bool "SEC2+ (SEC version 2.0 or upper)"
339 depends on CRYPTO_DEV_TALITOS
340 default y if !PPC_8xx
342 Say 'Y' here to use the Freescale Security Engine (SEC)
343 version 2 and following as found on MPC83xx, MPC85xx, etc ...
345 config CRYPTO_DEV_IXP4XX
346 tristate "Driver for IXP4xx crypto hardware acceleration"
347 depends on ARCH_IXP4XX && IXP4XX_QMGR && IXP4XX_NPE
353 select CRYPTO_LIB_DES
355 select CRYPTO_AUTHENC
356 select CRYPTO_SKCIPHER
358 Driver for the IXP4xx NPE crypto engine.
360 config CRYPTO_DEV_PPC4XX
361 tristate "Driver AMCC PPC4xx crypto accelerator"
362 depends on PPC && 4xx
366 select CRYPTO_LIB_AES
370 select CRYPTO_SKCIPHER
372 This option allows you to have support for AMCC crypto acceleration.
374 config HW_RANDOM_PPC4XX
375 bool "PowerPC 4xx generic true random number generator support"
376 depends on CRYPTO_DEV_PPC4XX && HW_RANDOM=y
379 This option provides the kernel-side support for the TRNG hardware
380 found in the security function of some PowerPC 4xx SoCs.
382 config CRYPTO_DEV_OMAP
383 tristate "Support for OMAP crypto HW accelerators"
384 depends on ARCH_OMAP2PLUS
386 OMAP processors have various crypto HW accelerators. Select this if
387 you want to use the OMAP modules for any of the crypto algorithms.
391 config CRYPTO_DEV_OMAP_SHAM
392 tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator"
393 depends on ARCH_OMAP2PLUS
401 OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you
402 want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
404 config CRYPTO_DEV_OMAP_AES
405 tristate "Support for OMAP AES hw engine"
406 depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS
408 select CRYPTO_SKCIPHER
415 OMAP processors have AES module accelerator. Select this if you
416 want to use the OMAP module for AES algorithms.
418 config CRYPTO_DEV_OMAP_DES
419 tristate "Support for OMAP DES/3DES hw engine"
420 depends on ARCH_OMAP2PLUS
421 select CRYPTO_LIB_DES
422 select CRYPTO_SKCIPHER
425 OMAP processors have DES/3DES module accelerator. Select this if you
426 want to use the OMAP module for DES and 3DES algorithms. Currently
427 the ECB and CBC modes of operation are supported by the driver. Also
428 accesses made on unaligned boundaries are supported.
430 endif # CRYPTO_DEV_OMAP
432 config CRYPTO_DEV_SAHARA
433 tristate "Support for SAHARA crypto accelerator"
434 depends on ARCH_MXC && OF
435 select CRYPTO_SKCIPHER
439 This option enables support for the SAHARA HW crypto accelerator
440 found in some Freescale i.MX chips.
442 config CRYPTO_DEV_EXYNOS_RNG
443 tristate "Exynos HW pseudo random number generator support"
444 depends on ARCH_EXYNOS || COMPILE_TEST
448 This driver provides kernel-side support through the
449 cryptographic API for the pseudo random number generator hardware
450 found on Exynos SoCs.
452 To compile this driver as a module, choose M here: the
453 module will be called exynos-rng.
457 config CRYPTO_DEV_S5P
458 tristate "Support for Samsung S5PV210/Exynos crypto accelerator"
459 depends on ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST
462 select CRYPTO_SKCIPHER
464 This option allows you to have support for S5P crypto acceleration.
465 Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES
466 algorithms execution.
468 config CRYPTO_DEV_EXYNOS_HASH
469 bool "Support for Samsung Exynos HASH accelerator"
470 depends on CRYPTO_DEV_S5P
471 depends on !CRYPTO_DEV_EXYNOS_RNG && CRYPTO_DEV_EXYNOS_RNG!=m
476 Select this to offload Exynos from HASH MD5/SHA1/SHA256.
477 This will select software SHA1, MD5 and SHA256 as they are
478 needed for small and zero-size messages.
479 HASH algorithms will be disabled if EXYNOS_RNG
480 is enabled due to hw conflict.
483 bool "Support for IBM PowerPC Nest (NX) cryptographic acceleration"
486 This enables support for the NX hardware cryptographic accelerator
487 coprocessor that is in IBM PowerPC P7+ or later processors. This
488 does not actually enable any drivers, it only allows you to select
489 which acceleration type (encryption and/or compression) to enable.
492 source "drivers/crypto/nx/Kconfig"
495 config CRYPTO_DEV_UX500
496 tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration"
497 depends on ARCH_U8500
499 Driver for ST-Ericsson UX500 crypto engine.
502 source "drivers/crypto/ux500/Kconfig"
503 endif # if CRYPTO_DEV_UX500
505 config CRYPTO_DEV_ATMEL_AUTHENC
506 bool "Support for Atmel IPSEC/SSL hw accelerator"
507 depends on ARCH_AT91 || COMPILE_TEST
508 depends on CRYPTO_DEV_ATMEL_AES
510 Some Atmel processors can combine the AES and SHA hw accelerators
511 to enhance support of IPSEC/SSL.
512 Select this if you want to use the Atmel modules for
513 authenc(hmac(shaX),Y(cbc)) algorithms.
515 config CRYPTO_DEV_ATMEL_AES
516 tristate "Support for Atmel AES hw accelerator"
517 depends on ARCH_AT91 || COMPILE_TEST
520 select CRYPTO_SKCIPHER
521 select CRYPTO_AUTHENC if CRYPTO_DEV_ATMEL_AUTHENC
522 select CRYPTO_DEV_ATMEL_SHA if CRYPTO_DEV_ATMEL_AUTHENC
524 Some Atmel processors have AES hw accelerator.
525 Select this if you want to use the Atmel module for
528 To compile this driver as a module, choose M here: the module
529 will be called atmel-aes.
531 config CRYPTO_DEV_ATMEL_TDES
532 tristate "Support for Atmel DES/TDES hw accelerator"
533 depends on ARCH_AT91 || COMPILE_TEST
534 select CRYPTO_LIB_DES
535 select CRYPTO_SKCIPHER
537 Some Atmel processors have DES/TDES hw accelerator.
538 Select this if you want to use the Atmel module for
541 To compile this driver as a module, choose M here: the module
542 will be called atmel-tdes.
544 config CRYPTO_DEV_ATMEL_SHA
545 tristate "Support for Atmel SHA hw accelerator"
546 depends on ARCH_AT91 || COMPILE_TEST
549 Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
551 Select this if you want to use the Atmel module for
552 SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
554 To compile this driver as a module, choose M here: the module
555 will be called atmel-sha.
557 config CRYPTO_DEV_ATMEL_I2C
561 config CRYPTO_DEV_ATMEL_ECC
562 tristate "Support for Microchip / Atmel ECC hw accelerator"
564 select CRYPTO_DEV_ATMEL_I2C
568 Microhip / Atmel ECC hw accelerator.
569 Select this if you want to use the Microchip / Atmel module for
572 To compile this driver as a module, choose M here: the module
573 will be called atmel-ecc.
575 config CRYPTO_DEV_ATMEL_SHA204A
576 tristate "Support for Microchip / Atmel SHA accelerator and RNG"
578 select CRYPTO_DEV_ATMEL_I2C
582 Microhip / Atmel SHA accelerator and RNG.
583 Select this if you want to use the Microchip / Atmel SHA204A
584 module as a random number generator. (Other functions of the
585 chip are currently not exposed by this driver)
587 To compile this driver as a module, choose M here: the module
588 will be called atmel-sha204a.
590 config CRYPTO_DEV_CCP
591 bool "Support for AMD Secure Processor"
592 depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM
594 The AMD Secure Processor provides support for the Cryptographic Coprocessor
595 (CCP) and the Platform Security Processor (PSP) devices.
598 source "drivers/crypto/ccp/Kconfig"
601 config CRYPTO_DEV_MXS_DCP
602 tristate "Support for Freescale MXS DCP"
603 depends on (ARCH_MXS || ARCH_MXC)
608 select CRYPTO_SKCIPHER
611 The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB
612 co-processor on the die.
614 To compile this driver as a module, choose M here: the module
615 will be called mxs-dcp.
617 source "drivers/crypto/qat/Kconfig"
618 source "drivers/crypto/cavium/cpt/Kconfig"
619 source "drivers/crypto/cavium/nitrox/Kconfig"
620 source "drivers/crypto/marvell/Kconfig"
622 config CRYPTO_DEV_CAVIUM_ZIP
623 tristate "Cavium ZIP driver"
624 depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
626 Select this option if you want to enable compression/decompression
627 acceleration on Cavium's ARM based SoCs
629 config CRYPTO_DEV_QCE
630 tristate "Qualcomm crypto engine accelerator"
631 depends on ARCH_QCOM || COMPILE_TEST
634 This driver supports Qualcomm crypto engine accelerator
635 hardware. To compile this driver as a module, choose M here. The
636 module will be called qcrypto.
638 config CRYPTO_DEV_QCE_SKCIPHER
640 depends on CRYPTO_DEV_QCE
642 select CRYPTO_LIB_DES
647 select CRYPTO_SKCIPHER
649 config CRYPTO_DEV_QCE_SHA
651 depends on CRYPTO_DEV_QCE
655 config CRYPTO_DEV_QCE_AEAD
657 depends on CRYPTO_DEV_QCE
658 select CRYPTO_AUTHENC
659 select CRYPTO_LIB_DES
662 prompt "Algorithms enabled for QCE acceleration"
663 default CRYPTO_DEV_QCE_ENABLE_ALL
664 depends on CRYPTO_DEV_QCE
666 This option allows to choose whether to build support for all algorithms
667 (default), hashes-only, or skciphers-only.
669 The QCE engine does not appear to scale as well as the CPU to handle
670 multiple crypto requests. While the ipq40xx chips have 4-core CPUs, the
671 QCE handles only 2 requests in parallel.
673 Ipsec throughput seems to improve when disabling either family of
674 algorithms, sharing the load with the CPU. Enabling skciphers-only
675 appears to work best.
677 config CRYPTO_DEV_QCE_ENABLE_ALL
678 bool "All supported algorithms"
679 select CRYPTO_DEV_QCE_SKCIPHER
680 select CRYPTO_DEV_QCE_SHA
681 select CRYPTO_DEV_QCE_AEAD
683 Enable all supported algorithms:
684 - AES (CBC, CTR, ECB, XTS)
688 - SHA256, HMAC-SHA256
690 config CRYPTO_DEV_QCE_ENABLE_SKCIPHER
691 bool "Symmetric-key ciphers only"
692 select CRYPTO_DEV_QCE_SKCIPHER
694 Enable symmetric-key ciphers only:
695 - AES (CBC, CTR, ECB, XTS)
699 config CRYPTO_DEV_QCE_ENABLE_SHA
700 bool "Hash/HMAC only"
701 select CRYPTO_DEV_QCE_SHA
703 Enable hashes/HMAC algorithms only:
705 - SHA256, HMAC-SHA256
707 config CRYPTO_DEV_QCE_ENABLE_AEAD
708 bool "AEAD algorithms only"
709 select CRYPTO_DEV_QCE_AEAD
711 Enable AEAD algorithms only:
717 config CRYPTO_DEV_QCE_SW_MAX_LEN
718 int "Default maximum request size to use software for AES"
719 depends on CRYPTO_DEV_QCE && CRYPTO_DEV_QCE_SKCIPHER
722 This sets the default maximum request size to perform AES requests
723 using software instead of the crypto engine. It can be changed by
724 setting the aes_sw_max_len parameter.
726 Small blocks are processed faster in software than hardware.
727 Considering the 256-bit ciphers, software is 2-3 times faster than
728 qce at 256-bytes, 30% faster at 512, and about even at 768-bytes.
729 With 128-bit keys, the break-even point would be around 1024-bytes.
731 The default is set a little lower, to 512 bytes, to balance the
732 cost in CPU usage. The minimum recommended setting is 16-bytes
733 (1 AES block), since AES-GCM will fail if you set it lower.
734 Setting this to zero will send all requests to the hardware.
736 Note that 192-bit keys are not supported by the hardware and are
737 always processed by the software fallback, and all DES requests
738 are done by the hardware.
740 config CRYPTO_DEV_QCOM_RNG
741 tristate "Qualcomm Random Number Generator Driver"
742 depends on ARCH_QCOM || COMPILE_TEST
745 This driver provides support for the Random Number
746 Generator hardware found on Qualcomm SoCs.
748 To compile this driver as a module, choose M here. The
749 module will be called qcom-rng. If unsure, say N.
751 config CRYPTO_DEV_VMX
752 bool "Support for VMX cryptographic acceleration instructions"
753 depends on PPC64 && VSX
755 Support for VMX cryptographic acceleration instructions.
757 source "drivers/crypto/vmx/Kconfig"
759 config CRYPTO_DEV_IMGTEC_HASH
760 tristate "Imagination Technologies hardware hash accelerator"
761 depends on MIPS || COMPILE_TEST
767 This driver interfaces with the Imagination Technologies
768 hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256
771 config CRYPTO_DEV_ROCKCHIP
772 tristate "Rockchip's Cryptographic Engine driver"
773 depends on OF && ARCH_ROCKCHIP
775 select CRYPTO_LIB_DES
780 select CRYPTO_SKCIPHER
783 This driver interfaces with the hardware crypto accelerator.
784 Supporting cbc/ecb chainmode, and aes/des/des3_ede cipher mode.
786 config CRYPTO_DEV_ZYNQMP_AES
787 tristate "Support for Xilinx ZynqMP AES hw accelerator"
788 depends on ZYNQMP_FIRMWARE || COMPILE_TEST
793 Xilinx ZynqMP has AES-GCM engine used for symmetric key
794 encryption and decryption. This driver interfaces with AES hw
795 accelerator. Select this if you want to use the ZynqMP module
798 source "drivers/crypto/chelsio/Kconfig"
800 source "drivers/crypto/virtio/Kconfig"
802 config CRYPTO_DEV_BCM_SPU
803 tristate "Broadcom symmetric crypto/hash acceleration support"
804 depends on ARCH_BCM_IPROC
807 select CRYPTO_AUTHENC
808 select CRYPTO_LIB_DES
814 This driver provides support for Broadcom crypto acceleration using the
815 Secure Processing Unit (SPU). The SPU driver registers skcipher,
816 ahash, and aead algorithms with the kernel cryptographic API.
818 source "drivers/crypto/stm32/Kconfig"
820 config CRYPTO_DEV_SAFEXCEL
821 tristate "Inside Secure's SafeXcel cryptographic engine driver"
822 depends on (OF || PCI || COMPILE_TEST) && HAS_IOMEM
823 select CRYPTO_LIB_AES
824 select CRYPTO_AUTHENC
825 select CRYPTO_SKCIPHER
826 select CRYPTO_LIB_DES
833 select CRYPTO_CHACHA20POLY1305
836 This driver interfaces with the SafeXcel EIP-97 and EIP-197 cryptographic
837 engines designed by Inside Secure. It currently accelerates DES, 3DES and
838 AES block ciphers in ECB and CBC mode, as well as SHA1, SHA224, SHA256,
839 SHA384 and SHA512 hash algorithms for both basic hash and HMAC.
840 Additionally, it accelerates combined AES-CBC/HMAC-SHA AEAD operations.
842 config CRYPTO_DEV_ARTPEC6
843 tristate "Support for Axis ARTPEC-6/7 hardware crypto acceleration."
844 depends on ARM && (ARCH_ARTPEC || COMPILE_TEST)
849 select CRYPTO_SKCIPHER
856 Enables the driver for the on-chip crypto accelerator
859 To compile this driver as a module, choose M here.
861 config CRYPTO_DEV_CCREE
862 tristate "Support for ARM TrustZone CryptoCell family of security processors"
863 depends on CRYPTO && CRYPTO_HW && OF && HAS_DMA
866 select CRYPTO_SKCIPHER
867 select CRYPTO_LIB_DES
869 select CRYPTO_AUTHENC
883 Say 'Y' to enable a driver for the REE interface of the Arm
884 TrustZone CryptoCell family of processors. Currently the
885 CryptoCell 713, 703, 712, 710 and 630 are supported.
886 Choose this if you wish to use hardware acceleration of
887 cryptographic operations on the system REE.
890 source "drivers/crypto/hisilicon/Kconfig"
892 source "drivers/crypto/amlogic/Kconfig"
894 config CRYPTO_DEV_SA2UL
895 tristate "Support for TI security accelerator"
896 depends on ARCH_K3 || COMPILE_TEST
899 select CRYPTO_AES_ARM64
901 select CRYPTO_AUTHENC
908 K3 devices include a security accelerator engine that may be
909 used for crypto offload. Select this if you want to use hardware
910 acceleration for cryptographic algorithms on these devices.
912 source "drivers/crypto/keembay/Kconfig"