# SPDX-License-Identifier: GPL-2.0-only menuconfig CRYPTO_HW bool "Hardware crypto devices" default y help Say Y here to get to see options for hardware crypto devices and processors. This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and disabled. if CRYPTO_HW source "drivers/crypto/allwinner/Kconfig" config CRYPTO_DEV_PADLOCK tristate "Support for VIA PadLock ACE" depends on X86 && !UML help Some VIA processors come with an integrated crypto engine (so called VIA PadLock ACE, Advanced Cryptography Engine) that provides instructions for very fast cryptographic operations with supported algorithms. The instructions are used only when the CPU supports them. Otherwise software encryption is used. config CRYPTO_DEV_PADLOCK_AES tristate "PadLock driver for AES algorithm" depends on CRYPTO_DEV_PADLOCK select CRYPTO_SKCIPHER select CRYPTO_LIB_AES help Use VIA PadLock for AES algorithm. Available in VIA C3 and newer CPUs. If unsure say M. The compiled module will be called padlock-aes. config CRYPTO_DEV_PADLOCK_SHA tristate "PadLock driver for SHA1 and SHA256 algorithms" depends on CRYPTO_DEV_PADLOCK select CRYPTO_HASH select CRYPTO_SHA1 select CRYPTO_SHA256 help Use VIA PadLock for SHA1/SHA256 algorithms. Available in VIA C7 and newer processors. If unsure say M. The compiled module will be called padlock-sha. config CRYPTO_DEV_GEODE tristate "Support for the Geode LX AES engine" depends on X86_32 && PCI select CRYPTO_ALGAPI select CRYPTO_SKCIPHER help Say 'Y' here to use the AMD Geode LX processor on-board AES engine for the CryptoAPI AES algorithm. To compile this driver as a module, choose M here: the module will be called geode-aes. config ZCRYPT tristate "Support for s390 cryptographic adapters" depends on S390 depends on AP select HW_RANDOM help Select this option if you want to enable support for s390 cryptographic adapters like Crypto Express 4 up to 8 in Coprocessor (CEXxC), EP11 Coprocessor (CEXxP) or Accelerator (CEXxA) mode. config PKEY tristate "Kernel API for protected key handling" depends on S390 help With this option enabled the pkey kernel modules provide an API for creation and handling of protected keys. Other parts of the kernel or userspace applications may use these functions. The protected key support is distributed into: - A pkey base and API kernel module (pkey.ko) which offers the infrastructure for the pkey handler kernel modules, the ioctl and the sysfs API and the in-kernel API to the crypto cipher implementations using protected key. - A pkey pckmo kernel module (pkey-pckmo.ko) which is automatically loaded when pckmo support (that is generation of protected keys from clear key values) is available. - A pkey CCA kernel module (pkey-cca.ko) which is automatically loaded when a CEX crypto card is available. - A pkey EP11 kernel module (pkey-ep11.ko) which is automatically loaded when a CEX crypto card is available. - A pkey UV kernel module (pkey-uv.ko) which is automatically loaded when the Ultravisor feature is available within a protected execution environment. Select this option if you want to enable the kernel and userspace API for protected key handling. config PKEY_CCA tristate "PKEY CCA support handler" depends on PKEY depends on ZCRYPT help This is the CCA support handler for deriving protected keys from CCA (secure) keys. Also this handler provides an alternate way to make protected keys from clear key values. The PKEY CCA support handler needs a Crypto Express card (CEX) in CCA mode. If you have selected the PKEY option then you should also enable this option unless you are sure you never need to derive protected keys from CCA key material. config PKEY_EP11 tristate "PKEY EP11 support handler" depends on PKEY depends on ZCRYPT help This is the EP11 support handler for deriving protected keys from EP11 (secure) keys. Also this handler provides an alternate way to make protected keys from clear key values. The PKEY EP11 support handler needs a Crypto Express card (CEX) in EP11 mode. If you have selected the PKEY option then you should also enable this option unless you are sure you never need to derive protected keys from EP11 key material. config PKEY_PCKMO tristate "PKEY PCKMO support handler" depends on PKEY help This is the PCKMO support handler for deriving protected keys from clear key values via invoking the PCKMO instruction. The PCKMO instruction can be enabled and disabled in the crypto settings at the LPAR profile. This handler checks for availability during initialization and if build as a kernel module unloads itself if PCKMO is disabled. The PCKMO way of deriving protected keys from clear key material is especially used during self test of protected key ciphers like PAES but the CCA and EP11 handler provide alternate ways to generate protected keys from clear key values. If you have selected the PKEY option then you should also enable this option unless you are sure you never need to derive protected keys from clear key values directly via PCKMO. config PKEY_UV tristate "PKEY UV support handler" depends on PKEY depends on S390_UV_UAPI help This is the PKEY Ultravisor support handler for deriving protected keys from secrets stored within the Ultravisor (UV). This module works together with the UV device and supports the retrieval of protected keys from secrets stored within the UV firmware layer. This service is only available within a protected execution guest and thus this module will fail upon modprobe if no protected execution environment is detected. Enable this option if you intend to run this kernel with an KVM guest with protected execution and you want to use UV retrievable secrets via PKEY API. config CRYPTO_PAES_S390 tristate "PAES cipher algorithms" depends on S390 depends on ZCRYPT depends on PKEY select CRYPTO_ALGAPI select CRYPTO_SKCIPHER select CRYPTO_ENGINE help This is the s390 hardware accelerated implementation of the AES cipher algorithms for use with protected key. Select this option if you want to use the paes cipher for example to use protected key encrypted devices. config CRYPTO_PHMAC_S390 tristate "PHMAC cipher algorithms" depends on S390 depends on PKEY select CRYPTO_HASH select CRYPTO_ENGINE help This is the s390 hardware accelerated implementation of the protected key HMAC support for SHA224, SHA256, SHA384 and SHA512. Select this option if you want to use the phmac digests for example to use dm-integrity with secure/protected keys. config S390_PRNG tristate "Pseudo random number generator device driver" depends on S390 default "m" help Select this option if you want to use the s390 pseudo random number generator. The PRNG is part of the cryptographic processor functions and uses triple-DES to generate secure random numbers like the ANSI X9.17 standard. User-space programs access the pseudo-random-number device through the char device /dev/prandom. It is available as of z9. config CRYPTO_DEV_SL3516 tristate "Storlink SL3516 crypto offloader" depends on ARCH_GEMINI || COMPILE_TEST depends on HAS_IOMEM && PM select CRYPTO_SKCIPHER select CRYPTO_ENGINE select CRYPTO_ECB select CRYPTO_AES select HW_RANDOM help This option allows you to have support for SL3516 crypto offloader. config CRYPTO_DEV_SL3516_DEBUG bool "Enable SL3516 stats" depends on CRYPTO_DEV_SL3516 depends on DEBUG_FS help Say y to enable SL3516 debug stats. This will create /sys/kernel/debug/sl3516/stats for displaying the number of requests per algorithm and other internal stats. config CRYPTO_DEV_HIFN_795X tristate "Driver HIFN 795x crypto accelerator chips" select CRYPTO_LIB_DES select CRYPTO_SKCIPHER select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG depends on PCI depends on !ARCH_DMA_ADDR_T_64BIT help This option allows you to have support for HIFN 795x crypto adapters. config CRYPTO_DEV_HIFN_795X_RNG bool "HIFN 795x random number generator" depends on CRYPTO_DEV_HIFN_795X help Select this option if you want to enable the random number generator on the HIFN 795x crypto adapters. source "drivers/crypto/caam/Kconfig" config CRYPTO_DEV_TALITOS tristate "Talitos Freescale Security Engine (SEC)" select CRYPTO_AEAD select CRYPTO_AUTHENC select CRYPTO_SKCIPHER select CRYPTO_HASH select CRYPTO_LIB_DES select HW_RANDOM depends on FSL_SOC help Say 'Y' here to use the Freescale Security Engine (SEC) to offload cryptographic algorithm computation. The Freescale SEC is present on PowerQUICC 'E' processors, such as the MPC8349E and MPC8548E. To compile this driver as a module, choose M here: the module will be called talitos. config CRYPTO_DEV_TALITOS1 bool "SEC1 (SEC 1.0 and SEC Lite 1.2)" depends on CRYPTO_DEV_TALITOS depends on PPC_8xx || PPC_82xx default y help Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0 found on MPC82xx or the Freescale Security Engine (SEC Lite) version 1.2 found on MPC8xx config CRYPTO_DEV_TALITOS2 bool "SEC2+ (SEC version 2.0 or upper)" depends on CRYPTO_DEV_TALITOS default y if !PPC_8xx help Say 'Y' here to use the Freescale Security Engine (SEC) version 2 and following as found on MPC83xx, MPC85xx, etc ... config CRYPTO_DEV_PPC4XX tristate "Driver AMCC PPC4xx crypto accelerator" depends on PPC && 4xx select CRYPTO_HASH select CRYPTO_AEAD select CRYPTO_AES select CRYPTO_LIB_AES select CRYPTO_CCM select CRYPTO_CTR select CRYPTO_GCM select CRYPTO_SKCIPHER help This option allows you to have support for AMCC crypto acceleration. config HW_RANDOM_PPC4XX bool "PowerPC 4xx generic true random number generator support" depends on CRYPTO_DEV_PPC4XX && HW_RANDOM=y default y help This option provides the kernel-side support for the TRNG hardware found in the security function of some PowerPC 4xx SoCs. config CRYPTO_DEV_OMAP tristate "Support for OMAP crypto HW accelerators" depends on ARCH_OMAP2PLUS || COMPILE_TEST help OMAP processors have various crypto HW accelerators. Select this if you want to use the OMAP modules for any of the crypto algorithms. if CRYPTO_DEV_OMAP config CRYPTO_DEV_OMAP_SHAM tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator" depends on ARCH_OMAP2PLUS select CRYPTO_ENGINE select CRYPTO_SHA1 select CRYPTO_MD5 select CRYPTO_SHA256 select CRYPTO_SHA512 select CRYPTO_HMAC help OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you want to use the OMAP module for MD5/SHA1/SHA2 algorithms. config CRYPTO_DEV_OMAP_AES tristate "Support for OMAP AES hw engine" depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS select CRYPTO_AES select CRYPTO_SKCIPHER select CRYPTO_ENGINE select CRYPTO_CBC select CRYPTO_ECB select CRYPTO_CTR select CRYPTO_AEAD help OMAP processors have AES module accelerator. Select this if you want to use the OMAP module for AES algorithms. config CRYPTO_DEV_OMAP_DES tristate "Support for OMAP DES/3DES hw engine" depends on ARCH_OMAP2PLUS || COMPILE_TEST select CRYPTO_LIB_DES select CRYPTO_SKCIPHER select CRYPTO_ENGINE help OMAP processors have DES/3DES module accelerator. Select this if you want to use the OMAP module for DES and 3DES algorithms. Currently the ECB and CBC modes of operation are supported by the driver. Also accesses made on unaligned boundaries are supported. endif # CRYPTO_DEV_OMAP config CRYPTO_DEV_SAHARA tristate "Support for SAHARA crypto accelerator" depends on ARCH_MXC && OF select CRYPTO_SKCIPHER select CRYPTO_AES select CRYPTO_ECB select CRYPTO_ENGINE help This option enables support for the SAHARA HW crypto accelerator found in some Freescale i.MX chips. config CRYPTO_DEV_S5P tristate "Support for Samsung S5PV210/Exynos crypto accelerator" depends on ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST depends on HAS_IOMEM select CRYPTO_AES select CRYPTO_SKCIPHER help This option allows you to have support for S5P crypto acceleration. Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES algorithms execution. config CRYPTO_DEV_EXYNOS_HASH bool "Support for Samsung Exynos HASH accelerator" depends on CRYPTO_DEV_S5P select CRYPTO_SHA1 select CRYPTO_MD5 select CRYPTO_SHA256 help Select this to offload Exynos from HASH MD5/SHA1/SHA256. This will select software SHA1, MD5 and SHA256 as they are needed for small and zero-size messages. config CRYPTO_DEV_NX bool "Support for IBM PowerPC Nest (NX) cryptographic acceleration" depends on PPC64 help This enables support for the NX hardware cryptographic accelerator coprocessor that is in IBM PowerPC P7+ or later processors. This does not actually enable any drivers, it only allows you to select which acceleration type (encryption and/or compression) to enable. if CRYPTO_DEV_NX source "drivers/crypto/nx/Kconfig"endif config CRYPTO_DEV_ATMEL_AUTHENC bool "Support for Atmel IPSEC/SSL hw accelerator" depends on ARCH_AT91 || COMPILE_TEST depends on CRYPTO_DEV_ATMEL_AES help Some Atmel processors can combine the AES and SHA hw accelerators to enhance support of IPSEC/SSL. Select this if you want to use the Atmel modules for authenc(hmac(shaX),Y(cbc)) algorithms. config CRYPTO_DEV_ATMEL_AES tristate "Support for Atmel AES hw accelerator" depends on ARCH_MICROCHIP || COMPILE_TEST select CRYPTO_AES select CRYPTO_AEAD select CRYPTO_SKCIPHER select CRYPTO_AUTHENC if CRYPTO_DEV_ATMEL_AUTHENC select CRYPTO_DEV_ATMEL_SHA if CRYPTO_DEV_ATMEL_AUTHENC help Some Atmel processors have AES hw accelerator. Select this if you want to use the Atmel module for AES algorithms. To compile this driver as a module, choose M here: the module will be called atmel-aes. config CRYPTO_DEV_ATMEL_TDES tristate "Support for Atmel DES/TDES hw accelerator" depends on ARCH_AT91 || COMPILE_TEST select CRYPTO_LIB_DES select CRYPTO_SKCIPHER help Some Atmel processors have DES/TDES hw accelerator. Select this if you want to use the Atmel module for DES/TDES algorithms. To compile this driver as a module, choose M here: the module will be called atmel-tdes. config CRYPTO_DEV_ATMEL_SHA tristate "Support for Atmel SHA hw accelerator" depends on ARCH_AT91 || COMPILE_TEST select CRYPTO_HASH help Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512 hw accelerator. Select this if you want to use the Atmel module for SHA1/SHA224/SHA256/SHA384/SHA512 algorithms. To compile this driver as a module, choose M here: the module will be called atmel-sha. config CRYPTO_DEV_ATMEL_I2C tristate select BITREVERSE config CRYPTO_DEV_ATMEL_ECC tristate "Support for Microchip / Atmel ECC hw accelerator" depends on I2C select CRYPTO_DEV_ATMEL_I2C select CRYPTO_ECDH select CRC16 help Microchip / Atmel ECC hw accelerator. Select this if you want to use the Microchip / Atmel module for ECDH algorithm. To compile this driver as a module, choose M here: the module will be called atmel-ecc. config CRYPTO_DEV_ATMEL_SHA204A tristate "Support for Microchip / Atmel SHA accelerator and RNG" depends on I2C select CRYPTO_DEV_ATMEL_I2C select HW_RANDOM select CRC16 help Microchip / Atmel SHA accelerator and RNG. Select this if you want to use the Microchip / Atmel SHA204A module as a random number generator. (Other functions of the chip are currently not exposed by this driver) To compile this driver as a module, choose M here: the module will be called atmel-sha204a. config CRYPTO_DEV_CCP bool "Support for AMD Secure Processor" depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM helpLines 1–500 of 834. Load more
# SPDX-License-Identifier: GPL-2.0-only menuconfig CRYPTO_HW bool "Hardware crypto devices" default y help Say Y here to get to see options for hardware crypto devices and processors. This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and disabled. if CRYPTO_HW source "drivers/crypto/allwinner/Kconfig" config CRYPTO_DEV_PADLOCK tristate "Support for VIA PadLock ACE" depends on X86 && !UML help Some VIA processors come with an integrated crypto engine (so called VIA PadLock ACE, Advanced Cryptography Engine) that provides instructions for very fast cryptographic operations with supported algorithms. The instructions are used only when the CPU supports them. Otherwise software encryption is used. config CRYPTO_DEV_PADLOCK_AES tristate "PadLock driver for AES algorithm" depends on CRYPTO_DEV_PADLOCK select CRYPTO_SKCIPHER select CRYPTO_LIB_AES help Use VIA PadLock for AES algorithm. Available in VIA C3 and newer CPUs. If unsure say M. The compiled module will be called padlock-aes. config CRYPTO_DEV_PADLOCK_SHA tristate "PadLock driver for SHA1 and SHA256 algorithms" depends on CRYPTO_DEV_PADLOCK select CRYPTO_HASH select CRYPTO_SHA1 select CRYPTO_SHA256 help Use VIA PadLock for SHA1/SHA256 algorithms. Available in VIA C7 and newer processors. If unsure say M. The compiled module will be called padlock-sha. config CRYPTO_DEV_GEODE tristate "Support for the Geode LX AES engine" depends on X86_32 && PCI select CRYPTO_ALGAPI select CRYPTO_SKCIPHER help Say 'Y' here to use the AMD Geode LX processor on-board AES engine for the CryptoAPI AES algorithm. To compile this driver as a module, choose M here: the module will be called geode-aes. config ZCRYPT tristate "Support for s390 cryptographic adapters" depends on S390 depends on AP select HW_RANDOM help Select this option if you want to enable support for s390 cryptographic adapters like Crypto Express 4 up to 8 in Coprocessor (CEXxC), EP11 Coprocessor (CEXxP) or Accelerator (CEXxA) mode. config PKEY tristate "Kernel API for protected key handling" depends on S390 help With this option enabled the pkey kernel modules provide an API for creation and handling of protected keys. Other parts of the kernel or userspace applications may use these functions. The protected key support is distributed into: - A pkey base and API kernel module (pkey.ko) which offers the infrastructure for the pkey handler kernel modules, the ioctl and the sysfs API and the in-kernel API to the crypto cipher implementations using protected key. - A pkey pckmo kernel module (pkey-pckmo.ko) which is automatically loaded when pckmo support (that is generation of protected keys from clear key values) is available. - A pkey CCA kernel module (pkey-cca.ko) which is automatically loaded when a CEX crypto card is available. - A pkey EP11 kernel module (pkey-ep11.ko) which is automatically loaded when a CEX crypto card is available. - A pkey UV kernel module (pkey-uv.ko) which is automatically loaded when the Ultravisor feature is available within a protected execution environment. Select this option if you want to enable the kernel and userspace API for protected key handling. config PKEY_CCA tristate "PKEY CCA support handler" depends on PKEY depends on ZCRYPT help This is the CCA support handler for deriving protected keys from CCA (secure) keys. Also this handler provides an alternate way to make protected keys from clear key values. The PKEY CCA support handler needs a Crypto Express card (CEX) in CCA mode. If you have selected the PKEY option then you should also enable this option unless you are sure you never need to derive protected keys from CCA key material. config PKEY_EP11 tristate "PKEY EP11 support handler" depends on PKEY depends on ZCRYPT help This is the EP11 support handler for deriving protected keys from EP11 (secure) keys. Also this handler provides an alternate way to make protected keys from clear key values. The PKEY EP11 support handler needs a Crypto Express card (CEX) in EP11 mode. If you have selected the PKEY option then you should also enable this option unless you are sure you never need to derive protected keys from EP11 key material. config PKEY_PCKMO tristate "PKEY PCKMO support handler" depends on PKEY help This is the PCKMO support handler for deriving protected keys from clear key values via invoking the PCKMO instruction. The PCKMO instruction can be enabled and disabled in the crypto settings at the LPAR profile. This handler checks for availability during initialization and if build as a kernel module unloads itself if PCKMO is disabled. The PCKMO way of deriving protected keys from clear key material is especially used during self test of protected key ciphers like PAES but the CCA and EP11 handler provide alternate ways to generate protected keys from clear key values. If you have selected the PKEY option then you should also enable this option unless you are sure you never need to derive protected keys from clear key values directly via PCKMO. config PKEY_UV tristate "PKEY UV support handler" depends on PKEY depends on S390_UV_UAPI help This is the PKEY Ultravisor support handler for deriving protected keys from secrets stored within the Ultravisor (UV). This module works together with the UV device and supports the retrieval of protected keys from secrets stored within the UV firmware layer. This service is only available within a protected execution guest and thus this module will fail upon modprobe if no protected execution environment is detected. Enable this option if you intend to run this kernel with an KVM guest with protected execution and you want to use UV retrievable secrets via PKEY API. config CRYPTO_PAES_S390 tristate "PAES cipher algorithms" depends on S390 depends on ZCRYPT depends on PKEY select CRYPTO_ALGAPI select CRYPTO_SKCIPHER select CRYPTO_ENGINE help This is the s390 hardware accelerated implementation of the AES cipher algorithms for use with protected key. Select this option if you want to use the paes cipher for example to use protected key encrypted devices. config CRYPTO_PHMAC_S390 tristate "PHMAC cipher algorithms" depends on S390 depends on PKEY select CRYPTO_HASH select CRYPTO_ENGINE help This is the s390 hardware accelerated implementation of the protected key HMAC support for SHA224, SHA256, SHA384 and SHA512. Select this option if you want to use the phmac digests for example to use dm-integrity with secure/protected keys. config S390_PRNG tristate "Pseudo random number generator device driver" depends on S390 default "m" help Select this option if you want to use the s390 pseudo random number generator. The PRNG is part of the cryptographic processor functions and uses triple-DES to generate secure random numbers like the ANSI X9.17 standard. User-space programs access the pseudo-random-number device through the char device /dev/prandom. It is available as of z9. config CRYPTO_DEV_SL3516 tristate "Storlink SL3516 crypto offloader" depends on ARCH_GEMINI || COMPILE_TEST depends on HAS_IOMEM && PM select CRYPTO_SKCIPHER select CRYPTO_ENGINE select CRYPTO_ECB select CRYPTO_AES select HW_RANDOM help This option allows you to have support for SL3516 crypto offloader. config CRYPTO_DEV_SL3516_DEBUG bool "Enable SL3516 stats" depends on CRYPTO_DEV_SL3516 depends on DEBUG_FS help Say y to enable SL3516 debug stats. This will create /sys/kernel/debug/sl3516/stats for displaying the number of requests per algorithm and other internal stats. config CRYPTO_DEV_HIFN_795X tristate "Driver HIFN 795x crypto accelerator chips" select CRYPTO_LIB_DES select CRYPTO_SKCIPHER select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG depends on PCI depends on !ARCH_DMA_ADDR_T_64BIT help This option allows you to have support for HIFN 795x crypto adapters. config CRYPTO_DEV_HIFN_795X_RNG bool "HIFN 795x random number generator" depends on CRYPTO_DEV_HIFN_795X help Select this option if you want to enable the random number generator on the HIFN 795x crypto adapters. source "drivers/crypto/caam/Kconfig" config CRYPTO_DEV_TALITOS tristate "Talitos Freescale Security Engine (SEC)" select CRYPTO_AEAD select CRYPTO_AUTHENC select CRYPTO_SKCIPHER select CRYPTO_HASH select CRYPTO_LIB_DES select HW_RANDOM depends on FSL_SOC help Say 'Y' here to use the Freescale Security Engine (SEC) to offload cryptographic algorithm computation. The Freescale SEC is present on PowerQUICC 'E' processors, such as the MPC8349E and MPC8548E. To compile this driver as a module, choose M here: the module will be called talitos. config CRYPTO_DEV_TALITOS1 bool "SEC1 (SEC 1.0 and SEC Lite 1.2)" depends on CRYPTO_DEV_TALITOS depends on PPC_8xx || PPC_82xx default y help Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0 found on MPC82xx or the Freescale Security Engine (SEC Lite) version 1.2 found on MPC8xx config CRYPTO_DEV_TALITOS2 bool "SEC2+ (SEC version 2.0 or upper)" depends on CRYPTO_DEV_TALITOS default y if !PPC_8xx help Say 'Y' here to use the Freescale Security Engine (SEC) version 2 and following as found on MPC83xx, MPC85xx, etc ... config CRYPTO_DEV_PPC4XX tristate "Driver AMCC PPC4xx crypto accelerator" depends on PPC && 4xx select CRYPTO_HASH select CRYPTO_AEAD select CRYPTO_AES select CRYPTO_LIB_AES select CRYPTO_CCM select CRYPTO_CTR select CRYPTO_GCM select CRYPTO_SKCIPHER help This option allows you to have support for AMCC crypto acceleration. config HW_RANDOM_PPC4XX bool "PowerPC 4xx generic true random number generator support" depends on CRYPTO_DEV_PPC4XX && HW_RANDOM=y default y help This option provides the kernel-side support for the TRNG hardware found in the security function of some PowerPC 4xx SoCs. config CRYPTO_DEV_OMAP tristate "Support for OMAP crypto HW accelerators" depends on ARCH_OMAP2PLUS || COMPILE_TEST help OMAP processors have various crypto HW accelerators. Select this if you want to use the OMAP modules for any of the crypto algorithms. if CRYPTO_DEV_OMAP config CRYPTO_DEV_OMAP_SHAM tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator" depends on ARCH_OMAP2PLUS select CRYPTO_ENGINE select CRYPTO_SHA1 select CRYPTO_MD5 select CRYPTO_SHA256 select CRYPTO_SHA512 select CRYPTO_HMAC help OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you want to use the OMAP module for MD5/SHA1/SHA2 algorithms. config CRYPTO_DEV_OMAP_AES tristate "Support for OMAP AES hw engine" depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS select CRYPTO_AES select CRYPTO_SKCIPHER select CRYPTO_ENGINE select CRYPTO_CBC select CRYPTO_ECB select CRYPTO_CTR select CRYPTO_AEAD help OMAP processors have AES module accelerator. Select this if you want to use the OMAP module for AES algorithms. config CRYPTO_DEV_OMAP_DES tristate "Support for OMAP DES/3DES hw engine" depends on ARCH_OMAP2PLUS || COMPILE_TEST select CRYPTO_LIB_DES select CRYPTO_SKCIPHER select CRYPTO_ENGINE help OMAP processors have DES/3DES module accelerator. Select this if you want to use the OMAP module for DES and 3DES algorithms. Currently the ECB and CBC modes of operation are supported by the driver. Also accesses made on unaligned boundaries are supported. endif # CRYPTO_DEV_OMAP config CRYPTO_DEV_SAHARA tristate "Support for SAHARA crypto accelerator" depends on ARCH_MXC && OF select CRYPTO_SKCIPHER select CRYPTO_AES select CRYPTO_ECB select CRYPTO_ENGINE help This option enables support for the SAHARA HW crypto accelerator found in some Freescale i.MX chips. config CRYPTO_DEV_S5P tristate "Support for Samsung S5PV210/Exynos crypto accelerator" depends on ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST depends on HAS_IOMEM select CRYPTO_AES select CRYPTO_SKCIPHER help This option allows you to have support for S5P crypto acceleration. Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES algorithms execution. config CRYPTO_DEV_EXYNOS_HASH bool "Support for Samsung Exynos HASH accelerator" depends on CRYPTO_DEV_S5P select CRYPTO_SHA1 select CRYPTO_MD5 select CRYPTO_SHA256 help Select this to offload Exynos from HASH MD5/SHA1/SHA256. This will select software SHA1, MD5 and SHA256 as they are needed for small and zero-size messages. config CRYPTO_DEV_NX bool "Support for IBM PowerPC Nest (NX) cryptographic acceleration" depends on PPC64 help This enables support for the NX hardware cryptographic accelerator coprocessor that is in IBM PowerPC P7+ or later processors. This does not actually enable any drivers, it only allows you to select which acceleration type (encryption and/or compression) to enable. if CRYPTO_DEV_NX source "drivers/crypto/nx/Kconfig" endif config CRYPTO_DEV_ATMEL_AUTHENC bool "Support for Atmel IPSEC/SSL hw accelerator" depends on ARCH_AT91 || COMPILE_TEST depends on CRYPTO_DEV_ATMEL_AES help Some Atmel processors can combine the AES and SHA hw accelerators to enhance support of IPSEC/SSL. Select this if you want to use the Atmel modules for authenc(hmac(shaX),Y(cbc)) algorithms. config CRYPTO_DEV_ATMEL_AES tristate "Support for Atmel AES hw accelerator" depends on ARCH_MICROCHIP || COMPILE_TEST select CRYPTO_AES select CRYPTO_AEAD select CRYPTO_SKCIPHER select CRYPTO_AUTHENC if CRYPTO_DEV_ATMEL_AUTHENC select CRYPTO_DEV_ATMEL_SHA if CRYPTO_DEV_ATMEL_AUTHENC help Some Atmel processors have AES hw accelerator. Select this if you want to use the Atmel module for AES algorithms. To compile this driver as a module, choose M here: the module will be called atmel-aes. config CRYPTO_DEV_ATMEL_TDES tristate "Support for Atmel DES/TDES hw accelerator" depends on ARCH_AT91 || COMPILE_TEST select CRYPTO_LIB_DES select CRYPTO_SKCIPHER help Some Atmel processors have DES/TDES hw accelerator. Select this if you want to use the Atmel module for DES/TDES algorithms. To compile this driver as a module, choose M here: the module will be called atmel-tdes. config CRYPTO_DEV_ATMEL_SHA tristate "Support for Atmel SHA hw accelerator" depends on ARCH_AT91 || COMPILE_TEST select CRYPTO_HASH help Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512 hw accelerator. Select this if you want to use the Atmel module for SHA1/SHA224/SHA256/SHA384/SHA512 algorithms. To compile this driver as a module, choose M here: the module will be called atmel-sha. config CRYPTO_DEV_ATMEL_I2C tristate select BITREVERSE config CRYPTO_DEV_ATMEL_ECC tristate "Support for Microchip / Atmel ECC hw accelerator" depends on I2C select CRYPTO_DEV_ATMEL_I2C select CRYPTO_ECDH select CRC16 help Microchip / Atmel ECC hw accelerator. Select this if you want to use the Microchip / Atmel module for ECDH algorithm. To compile this driver as a module, choose M here: the module will be called atmel-ecc. config CRYPTO_DEV_ATMEL_SHA204A tristate "Support for Microchip / Atmel SHA accelerator and RNG" depends on I2C select CRYPTO_DEV_ATMEL_I2C select HW_RANDOM select CRC16 help Microchip / Atmel SHA accelerator and RNG. Select this if you want to use the Microchip / Atmel SHA204A module as a random number generator. (Other functions of the chip are currently not exposed by this driver) To compile this driver as a module, choose M here: the module will be called atmel-sha204a. config CRYPTO_DEV_CCP bool "Support for AMD Secure Processor" depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM help