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_32 && !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
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 PCI-attached cryptographic adapters"
67 select ZCRYPT_MONOLITHIC if ZCRYPT="y"
70 Select this option if you want to use a PCI-attached cryptographic
72 + PCI Cryptographic Accelerator (PCICA)
73 + PCI Cryptographic Coprocessor (PCICC)
74 + PCI-X Cryptographic Coprocessor (PCIXCC)
75 + Crypto Express2 Coprocessor (CEX2C)
76 + Crypto Express2 Accelerator (CEX2A)
78 config ZCRYPT_MONOLITHIC
79 bool "Monolithic zcrypt module"
82 Select this option if you want to have a single module z90crypt.ko
83 that contains all parts of the crypto device driver (ap bus,
84 request router and all the card drivers).
87 tristate "Support for OMAP SHA1/MD5 hw engine"
88 depends on ARCH_OMAP24XX && CRYPTO_SHA1 && CRYPTO_MD5
90 OMAP processors have SHA1/MD5 module accelerator. Select this if you
91 want to use the OMAP module for SHA1/MD5 algorithms.
93 config CRYPTO_SHA1_S390
94 tristate "SHA1 digest algorithm"
98 This is the s390 hardware accelerated implementation of the
99 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
101 config CRYPTO_SHA256_S390
102 tristate "SHA256 digest algorithm"
106 This is the s390 hardware accelerated implementation of the
107 SHA256 secure hash standard (DFIPS 180-2).
109 This version of SHA implements a 256 bit hash with 128 bits of
110 security against collision attacks.
112 config CRYPTO_SHA512_S390
113 tristate "SHA384 and SHA512 digest algorithm"
117 This is the s390 hardware accelerated implementation of the
118 SHA512 secure hash standard.
120 This version of SHA implements a 512 bit hash with 256 bits of
121 security against collision attacks. The code also includes SHA-384,
122 a 384 bit hash with 192 bits of security against collision attacks.
125 config CRYPTO_DES_S390
126 tristate "DES and Triple DES cipher algorithms"
129 select CRYPTO_BLKCIPHER
131 This us the s390 hardware accelerated implementation of the
132 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
134 config CRYPTO_AES_S390
135 tristate "AES cipher algorithms"
138 select CRYPTO_BLKCIPHER
140 This is the s390 hardware accelerated implementation of the
141 AES cipher algorithms (FIPS-197). AES uses the Rijndael
144 Rijndael appears to be consistently a very good performer in
145 both hardware and software across a wide range of computing
146 environments regardless of its use in feedback or non-feedback
147 modes. Its key setup time is excellent, and its key agility is
148 good. Rijndael's very low memory requirements make it very well
149 suited for restricted-space environments, in which it also
150 demonstrates excellent performance. Rijndael's operations are
151 among the easiest to defend against power and timing attacks.
153 On s390 the System z9-109 currently only supports the key size
157 tristate "Pseudo random number generator device driver"
161 Select this option if you want to use the s390 pseudo random number
162 generator. The PRNG is part of the cryptographic processor functions
163 and uses triple-DES to generate secure random numbers like the
164 ANSI X9.17 standard. The PRNG is usable via the char device
167 config CRYPTO_DEV_HIFN_795X
168 tristate "Driver HIFN 795x crypto accelerator chips"
171 select CRYPTO_BLKCIPHER
172 select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG
175 This option allows you to have support for HIFN 795x crypto adapters.
177 config CRYPTO_DEV_HIFN_795X_RNG
178 bool "HIFN 795x random number generator"
179 depends on CRYPTO_DEV_HIFN_795X
181 Select this option if you want to enable the random number generator
182 on the HIFN 795x crypto adapters.
184 config CRYPTO_DEV_TALITOS
185 tristate "Talitos Freescale Security Engine (SEC)"
187 select CRYPTO_AUTHENC
191 Say 'Y' here to use the Freescale Security Engine (SEC)
192 to offload cryptographic algorithm computation.
194 The Freescale SEC is present on PowerQUICC 'E' processors, such
195 as the MPC8349E and MPC8548E.
197 To compile this driver as a module, choose M here: the module
198 will be called talitos.
200 config CRYPTO_DEV_IXP4XX
201 tristate "Driver for IXP4xx crypto hardware acceleration"
202 depends on ARCH_IXP4XX
205 select CRYPTO_AUTHENC
206 select CRYPTO_BLKCIPHER
208 Driver for the IXP4xx NPE crypto engine.