2007-07-16 08:39:36 +02:00
|
|
|
|
|
|
|
menuconfig CRYPTO_HW
|
|
|
|
bool "Hardware crypto devices"
|
|
|
|
default y
|
2007-08-18 12:56:21 +02:00
|
|
|
---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.
|
2007-07-16 08:39:36 +02:00
|
|
|
|
|
|
|
if CRYPTO_HW
|
2005-04-17 00:20:36 +02:00
|
|
|
|
|
|
|
config CRYPTO_DEV_PADLOCK
|
2007-05-18 05:17:22 +02:00
|
|
|
tristate "Support for VIA PadLock ACE"
|
2009-04-22 07:00:15 +02:00
|
|
|
depends on X86 && !UML
|
2005-04-17 00:20:36 +02:00
|
|
|
help
|
|
|
|
Some VIA processors come with an integrated crypto engine
|
|
|
|
(so called VIA PadLock ACE, Advanced Cryptography Engine)
|
2006-08-06 14:46:20 +02:00
|
|
|
that provides instructions for very fast cryptographic
|
|
|
|
operations with supported algorithms.
|
2005-04-17 00:20:36 +02:00
|
|
|
|
|
|
|
The instructions are used only when the CPU supports them.
|
2006-08-06 14:50:30 +02:00
|
|
|
Otherwise software encryption is used.
|
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
config CRYPTO_DEV_PADLOCK_AES
|
2006-08-06 14:46:20 +02:00
|
|
|
tristate "PadLock driver for AES algorithm"
|
2005-04-17 00:20:36 +02:00
|
|
|
depends on CRYPTO_DEV_PADLOCK
|
2006-08-21 13:38:42 +02:00
|
|
|
select CRYPTO_BLKCIPHER
|
2008-04-01 15:24:50 +02:00
|
|
|
select CRYPTO_AES
|
2005-04-17 00:20:36 +02:00
|
|
|
help
|
|
|
|
Use VIA PadLock for AES algorithm.
|
|
|
|
|
2006-08-06 14:46:20 +02:00
|
|
|
Available in VIA C3 and newer CPUs.
|
|
|
|
|
|
|
|
If unsure say M. The compiled module will be
|
2009-06-05 00:44:53 +02:00
|
|
|
called padlock-aes.
|
2006-08-06 14:46:20 +02:00
|
|
|
|
2006-07-12 04:29:38 +02:00
|
|
|
config CRYPTO_DEV_PADLOCK_SHA
|
|
|
|
tristate "PadLock driver for SHA1 and SHA256 algorithms"
|
|
|
|
depends on CRYPTO_DEV_PADLOCK
|
2009-07-11 12:16:16 +02:00
|
|
|
select CRYPTO_HASH
|
2006-07-12 04:29:38 +02:00
|
|
|
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
|
2009-06-05 00:44:53 +02:00
|
|
|
called padlock-sha.
|
2006-07-12 04:29:38 +02:00
|
|
|
|
2006-10-04 10:48:57 +02:00
|
|
|
config CRYPTO_DEV_GEODE
|
|
|
|
tristate "Support for the Geode LX AES engine"
|
2007-05-02 14:08:26 +02:00
|
|
|
depends on X86_32 && PCI
|
2006-10-04 10:48:57 +02:00
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
help
|
|
|
|
Say 'Y' here to use the AMD Geode LX processor on-board AES
|
2007-05-09 07:12:20 +02:00
|
|
|
engine for the CryptoAPI AES algorithm.
|
2006-10-04 10:48:57 +02:00
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called geode-aes.
|
|
|
|
|
2007-05-10 15:46:00 +02:00
|
|
|
config ZCRYPT
|
|
|
|
tristate "Support for PCI-attached cryptographic adapters"
|
|
|
|
depends on S390
|
2008-04-17 07:46:15 +02:00
|
|
|
select HW_RANDOM
|
2007-05-10 15:46:00 +02:00
|
|
|
help
|
|
|
|
Select this option if you want to use a PCI-attached cryptographic
|
|
|
|
adapter like:
|
|
|
|
+ PCI Cryptographic Accelerator (PCICA)
|
|
|
|
+ PCI Cryptographic Coprocessor (PCICC)
|
|
|
|
+ PCI-X Cryptographic Coprocessor (PCIXCC)
|
|
|
|
+ Crypto Express2 Coprocessor (CEX2C)
|
|
|
|
+ Crypto Express2 Accelerator (CEX2A)
|
2011-05-23 10:24:30 +02:00
|
|
|
+ Crypto Express3 Coprocessor (CEX3C)
|
|
|
|
+ Crypto Express3 Accelerator (CEX3A)
|
2007-05-10 15:46:00 +02:00
|
|
|
|
2008-01-26 14:11:07 +01:00
|
|
|
config CRYPTO_SHA1_S390
|
|
|
|
tristate "SHA1 digest algorithm"
|
|
|
|
depends on S390
|
2009-01-18 10:33:33 +01:00
|
|
|
select CRYPTO_HASH
|
2008-01-26 14:11:07 +01:00
|
|
|
help
|
|
|
|
This is the s390 hardware accelerated implementation of the
|
|
|
|
SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
|
|
|
|
|
2011-04-19 21:29:19 +02:00
|
|
|
It is available as of z990.
|
|
|
|
|
2008-01-26 14:11:07 +01:00
|
|
|
config CRYPTO_SHA256_S390
|
|
|
|
tristate "SHA256 digest algorithm"
|
|
|
|
depends on S390
|
2009-01-18 10:33:33 +01:00
|
|
|
select CRYPTO_HASH
|
2008-01-26 14:11:07 +01:00
|
|
|
help
|
|
|
|
This is the s390 hardware accelerated implementation of the
|
|
|
|
SHA256 secure hash standard (DFIPS 180-2).
|
|
|
|
|
2011-04-19 21:29:19 +02:00
|
|
|
It is available as of z9.
|
2008-01-26 14:11:07 +01:00
|
|
|
|
2008-03-06 12:52:00 +01:00
|
|
|
config CRYPTO_SHA512_S390
|
2008-03-06 12:53:50 +01:00
|
|
|
tristate "SHA384 and SHA512 digest algorithm"
|
2008-03-06 12:52:00 +01:00
|
|
|
depends on S390
|
2009-01-18 10:33:33 +01:00
|
|
|
select CRYPTO_HASH
|
2008-03-06 12:52:00 +01:00
|
|
|
help
|
|
|
|
This is the s390 hardware accelerated implementation of the
|
|
|
|
SHA512 secure hash standard.
|
|
|
|
|
2011-04-19 21:29:19 +02:00
|
|
|
It is available as of z10.
|
2008-03-06 12:52:00 +01:00
|
|
|
|
2008-01-26 14:11:07 +01:00
|
|
|
config CRYPTO_DES_S390
|
|
|
|
tristate "DES and Triple DES cipher algorithms"
|
|
|
|
depends on S390
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_BLKCIPHER
|
2012-05-09 16:27:35 +02:00
|
|
|
select CRYPTO_DES
|
2008-01-26 14:11:07 +01:00
|
|
|
help
|
2011-05-04 07:09:44 +02:00
|
|
|
This is the s390 hardware accelerated implementation of the
|
2008-01-26 14:11:07 +01:00
|
|
|
DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
|
|
|
|
|
2011-05-04 07:09:44 +02:00
|
|
|
As of z990 the ECB and CBC mode are hardware accelerated.
|
|
|
|
As of z196 the CTR mode is hardware accelerated.
|
|
|
|
|
2008-01-26 14:11:07 +01:00
|
|
|
config CRYPTO_AES_S390
|
|
|
|
tristate "AES cipher algorithms"
|
|
|
|
depends on S390
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
help
|
|
|
|
This is the s390 hardware accelerated implementation of the
|
2011-04-26 08:12:42 +02:00
|
|
|
AES cipher algorithms (FIPS-197).
|
|
|
|
|
|
|
|
As of z9 the ECB and CBC modes are hardware accelerated
|
|
|
|
for 128 bit keys.
|
|
|
|
As of z10 the ECB and CBC modes are hardware accelerated
|
|
|
|
for all AES key sizes.
|
2011-05-04 07:09:44 +02:00
|
|
|
As of z196 the CTR mode is hardware accelerated for all AES
|
|
|
|
key sizes and XTS mode is hardware accelerated for 256 and
|
2011-04-26 08:12:42 +02:00
|
|
|
512 bit keys.
|
2008-01-26 14:11:07 +01:00
|
|
|
|
|
|
|
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
|
2011-04-19 21:29:19 +02:00
|
|
|
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.
|
2008-01-26 14:11:07 +01:00
|
|
|
|
2011-04-19 21:29:18 +02:00
|
|
|
config CRYPTO_GHASH_S390
|
|
|
|
tristate "GHASH digest algorithm"
|
|
|
|
depends on S390
|
|
|
|
select CRYPTO_HASH
|
|
|
|
help
|
|
|
|
This is the s390 hardware accelerated implementation of the
|
|
|
|
GHASH message digest algorithm for GCM (Galois/Counter Mode).
|
|
|
|
|
|
|
|
It is available as of z196.
|
|
|
|
|
2009-08-10 04:50:03 +02:00
|
|
|
config CRYPTO_DEV_MV_CESA
|
|
|
|
tristate "Marvell's Cryptographic Engine"
|
|
|
|
depends on PLAT_ORION
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_AES
|
|
|
|
select CRYPTO_BLKCIPHER2
|
2012-05-12 10:45:08 +02:00
|
|
|
select CRYPTO_HASH
|
2009-08-10 04:50:03 +02:00
|
|
|
help
|
|
|
|
This driver allows you to utilize the Cryptographic Engines and
|
|
|
|
Security Accelerator (CESA) which can be found on the Marvell Orion
|
|
|
|
and Kirkwood SoCs, such as QNAP's TS-209.
|
|
|
|
|
|
|
|
Currently the driver supports AES in ECB and CBC mode without DMA.
|
|
|
|
|
2010-05-19 06:14:04 +02:00
|
|
|
config CRYPTO_DEV_NIAGARA2
|
|
|
|
tristate "Niagara2 Stream Processing Unit driver"
|
2010-09-12 04:44:21 +02:00
|
|
|
select CRYPTO_DES
|
2010-05-19 06:14:04 +02:00
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
depends on SPARC64
|
|
|
|
help
|
|
|
|
Each core of a Niagara2 processor contains a Stream
|
|
|
|
Processing Unit, which itself contains several cryptographic
|
|
|
|
sub-units. One set provides the Modular Arithmetic Unit,
|
|
|
|
used for SSL offload. The other set provides the Cipher
|
|
|
|
Group, which can perform encryption, decryption, hashing,
|
|
|
|
checksumming, and raw copies.
|
|
|
|
|
2007-10-26 15:31:14 +02:00
|
|
|
config CRYPTO_DEV_HIFN_795X
|
|
|
|
tristate "Driver HIFN 795x crypto accelerator chips"
|
2007-10-11 13:58:16 +02:00
|
|
|
select CRYPTO_DES
|
2007-10-26 15:31:14 +02:00
|
|
|
select CRYPTO_ALGAPI
|
2007-11-27 12:48:27 +01:00
|
|
|
select CRYPTO_BLKCIPHER
|
2008-01-25 23:48:44 +01:00
|
|
|
select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG
|
2007-11-12 14:56:38 +01:00
|
|
|
depends on PCI
|
2011-10-10 12:55:41 +02:00
|
|
|
depends on !ARCH_DMA_ADDR_T_64BIT
|
2007-10-26 15:31:14 +02:00
|
|
|
help
|
|
|
|
This option allows you to have support for HIFN 795x crypto adapters.
|
|
|
|
|
2008-01-25 23:48:44 +01:00
|
|
|
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.
|
2007-10-26 15:31:14 +02:00
|
|
|
|
2011-03-13 09:54:26 +01:00
|
|
|
source drivers/crypto/caam/Kconfig
|
|
|
|
|
2008-06-23 13:50:15 +02:00
|
|
|
config CRYPTO_DEV_TALITOS
|
|
|
|
tristate "Talitos Freescale Security Engine (SEC)"
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_AUTHENC
|
|
|
|
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.
|
|
|
|
|
2008-06-25 08:38:47 +02:00
|
|
|
config CRYPTO_DEV_IXP4XX
|
|
|
|
tristate "Driver for IXP4xx crypto hardware acceleration"
|
2010-03-25 23:56:05 +01:00
|
|
|
depends on ARCH_IXP4XX && IXP4XX_QMGR && IXP4XX_NPE
|
2008-06-25 08:38:47 +02:00
|
|
|
select CRYPTO_DES
|
|
|
|
select CRYPTO_ALGAPI
|
2008-07-13 14:12:11 +02:00
|
|
|
select CRYPTO_AUTHENC
|
2008-06-25 08:38:47 +02:00
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
help
|
|
|
|
Driver for the IXP4xx NPE crypto engine.
|
|
|
|
|
2009-02-05 06:18:13 +01:00
|
|
|
config CRYPTO_DEV_PPC4XX
|
|
|
|
tristate "Driver AMCC PPC4xx crypto accelerator"
|
|
|
|
depends on PPC && 4xx
|
|
|
|
select CRYPTO_HASH
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
help
|
|
|
|
This option allows you to have support for AMCC crypto acceleration.
|
|
|
|
|
2010-05-03 05:10:59 +02:00
|
|
|
config CRYPTO_DEV_OMAP_SHAM
|
2013-07-26 08:59:14 +02:00
|
|
|
tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator"
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2010-05-03 05:10:59 +02:00
|
|
|
select CRYPTO_SHA1
|
|
|
|
select CRYPTO_MD5
|
2013-07-26 08:59:14 +02:00
|
|
|
select CRYPTO_SHA256
|
|
|
|
select CRYPTO_SHA512
|
|
|
|
select CRYPTO_HMAC
|
2010-05-03 05:10:59 +02:00
|
|
|
help
|
2013-07-26 08:59:14 +02:00
|
|
|
OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you
|
|
|
|
want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
|
2010-05-03 05:10:59 +02:00
|
|
|
|
2010-09-03 13:16:02 +02:00
|
|
|
config CRYPTO_DEV_OMAP_AES
|
|
|
|
tristate "Support for OMAP AES hw engine"
|
2013-08-18 04:42:35 +02:00
|
|
|
depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS
|
2010-09-03 13:16:02 +02:00
|
|
|
select CRYPTO_AES
|
2012-10-31 20:08:37 +01:00
|
|
|
select CRYPTO_BLKCIPHER2
|
2010-09-03 13:16:02 +02:00
|
|
|
help
|
|
|
|
OMAP processors have AES module accelerator. Select this if you
|
|
|
|
want to use the OMAP module for AES algorithms.
|
|
|
|
|
2011-02-21 06:43:21 +01:00
|
|
|
config CRYPTO_DEV_PICOXCELL
|
|
|
|
tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
|
2011-10-20 14:10:26 +02:00
|
|
|
depends on ARCH_PICOXCELL && HAVE_CLK
|
2011-02-21 06:43:21 +01:00
|
|
|
select CRYPTO_AES
|
|
|
|
select CRYPTO_AUTHENC
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_DES
|
|
|
|
select CRYPTO_CBC
|
|
|
|
select CRYPTO_ECB
|
|
|
|
select CRYPTO_SEQIV
|
|
|
|
help
|
|
|
|
This option enables support for the hardware offload engines in the
|
|
|
|
Picochip picoXcell SoC devices. Select this for IPSEC ESP offload
|
|
|
|
and for 3gpp Layer 2 ciphering support.
|
|
|
|
|
|
|
|
Saying m here will build a module named pipcoxcell_crypto.
|
|
|
|
|
2013-03-01 12:37:53 +01:00
|
|
|
config CRYPTO_DEV_SAHARA
|
|
|
|
tristate "Support for SAHARA crypto accelerator"
|
2013-05-12 13:57:19 +02:00
|
|
|
depends on ARCH_MXC && OF
|
2013-03-01 12:37:53 +01:00
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
select CRYPTO_AES
|
|
|
|
select CRYPTO_ECB
|
|
|
|
help
|
|
|
|
This option enables support for the SAHARA HW crypto accelerator
|
|
|
|
found in some Freescale i.MX chips.
|
|
|
|
|
2013-05-19 21:59:38 +02:00
|
|
|
config CRYPTO_DEV_DCP
|
|
|
|
tristate "Support for the DCP engine"
|
|
|
|
depends on ARCH_MXS && OF
|
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
select CRYPTO_AES
|
|
|
|
select CRYPTO_CBC
|
|
|
|
help
|
|
|
|
This options enables support for the hardware crypto-acceleration
|
|
|
|
capabilities of the DCP co-processor
|
|
|
|
|
2011-04-08 14:40:51 +02:00
|
|
|
config CRYPTO_DEV_S5P
|
|
|
|
tristate "Support for Samsung S5PV210 crypto accelerator"
|
|
|
|
depends on ARCH_S5PV210
|
|
|
|
select CRYPTO_AES
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
help
|
|
|
|
This option allows you to have support for S5P crypto acceleration.
|
|
|
|
Select this to offload Samsung S5PV210 or S5PC110 from AES
|
|
|
|
algorithms execution.
|
|
|
|
|
2012-01-13 06:38:37 +01:00
|
|
|
config CRYPTO_DEV_TEGRA_AES
|
|
|
|
tristate "Support for TEGRA AES hw engine"
|
|
|
|
depends on ARCH_TEGRA
|
|
|
|
select CRYPTO_AES
|
|
|
|
help
|
|
|
|
TEGRA processors have AES module accelerator. Select this if you
|
|
|
|
want to use the TEGRA module for AES algorithms.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called tegra-aes.
|
|
|
|
|
2012-04-12 07:39:26 +02:00
|
|
|
config CRYPTO_DEV_NX
|
2012-07-19 16:42:38 +02:00
|
|
|
bool "Support for IBM Power7+ in-Nest cryptographic acceleration"
|
2012-04-12 07:39:26 +02:00
|
|
|
depends on PPC64 && IBMVIO
|
2012-07-19 16:42:38 +02:00
|
|
|
default n
|
2012-04-12 07:39:26 +02:00
|
|
|
help
|
2012-07-19 16:42:38 +02:00
|
|
|
Support for Power7+ in-Nest cryptographic acceleration.
|
|
|
|
|
|
|
|
if CRYPTO_DEV_NX
|
|
|
|
source "drivers/crypto/nx/Kconfig"
|
|
|
|
endif
|
2012-04-12 07:39:26 +02:00
|
|
|
|
2012-04-30 10:11:17 +02:00
|
|
|
config CRYPTO_DEV_UX500
|
|
|
|
tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration"
|
|
|
|
depends on ARCH_U8500
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
help
|
|
|
|
Driver for ST-Ericsson UX500 crypto engine.
|
|
|
|
|
|
|
|
if CRYPTO_DEV_UX500
|
|
|
|
source "drivers/crypto/ux500/Kconfig"
|
|
|
|
endif # if CRYPTO_DEV_UX500
|
|
|
|
|
2012-06-04 06:24:47 +02:00
|
|
|
config CRYPTO_DEV_BFIN_CRC
|
|
|
|
tristate "Support for Blackfin CRC hardware"
|
|
|
|
depends on BF60x
|
|
|
|
help
|
|
|
|
Newer Blackfin processors have CRC hardware. Select this if you
|
|
|
|
want to use the Blackfin CRC module.
|
|
|
|
|
2012-07-01 19:19:44 +02:00
|
|
|
config CRYPTO_DEV_ATMEL_AES
|
|
|
|
tristate "Support for Atmel AES hw accelerator"
|
|
|
|
depends on ARCH_AT91
|
|
|
|
select CRYPTO_CBC
|
|
|
|
select CRYPTO_ECB
|
|
|
|
select CRYPTO_AES
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_BLKCIPHER
|
2012-08-07 14:02:14 +02:00
|
|
|
select AT_HDMAC
|
2012-07-01 19:19:44 +02:00
|
|
|
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.
|
|
|
|
|
2012-07-01 19:19:45 +02:00
|
|
|
config CRYPTO_DEV_ATMEL_TDES
|
|
|
|
tristate "Support for Atmel DES/TDES hw accelerator"
|
|
|
|
depends on ARCH_AT91
|
|
|
|
select CRYPTO_DES
|
|
|
|
select CRYPTO_CBC
|
|
|
|
select CRYPTO_ECB
|
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
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.
|
|
|
|
|
2012-07-01 19:19:46 +02:00
|
|
|
config CRYPTO_DEV_ATMEL_SHA
|
2013-02-20 17:10:26 +01:00
|
|
|
tristate "Support for Atmel SHA hw accelerator"
|
2012-07-01 19:19:46 +02:00
|
|
|
depends on ARCH_AT91
|
|
|
|
select CRYPTO_SHA1
|
|
|
|
select CRYPTO_SHA256
|
2013-02-20 17:10:26 +01:00
|
|
|
select CRYPTO_SHA512
|
2012-07-01 19:19:46 +02:00
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
help
|
2013-02-20 17:10:26 +01:00
|
|
|
Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
|
|
|
|
hw accelerator.
|
2012-07-01 19:19:46 +02:00
|
|
|
Select this if you want to use the Atmel module for
|
2013-02-20 17:10:26 +01:00
|
|
|
SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
|
2012-07-01 19:19:46 +02:00
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called atmel-sha.
|
|
|
|
|
2007-07-16 08:39:36 +02:00
|
|
|
endif # CRYPTO_HW
|