1 2menuconfig CRYPTO_HW 3 bool "Hardware crypto devices" 4 default y 5 ---help--- 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. 8 9 If you say N, all options in this submenu will be skipped and disabled. 10 11if CRYPTO_HW 12 13config CRYPTO_DEV_PADLOCK 14 tristate "Support for VIA PadLock ACE" 15 depends on X86 && !UML 16 help 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. 21 22 The instructions are used only when the CPU supports them. 23 Otherwise software encryption is used. 24 25config CRYPTO_DEV_PADLOCK_AES 26 tristate "PadLock driver for AES algorithm" 27 depends on CRYPTO_DEV_PADLOCK 28 select CRYPTO_BLKCIPHER 29 select CRYPTO_AES 30 help 31 Use VIA PadLock for AES algorithm. 32 33 Available in VIA C3 and newer CPUs. 34 35 If unsure say M. The compiled module will be 36 called padlock-aes. 37 38config CRYPTO_DEV_PADLOCK_SHA 39 tristate "PadLock driver for SHA1 and SHA256 algorithms" 40 depends on CRYPTO_DEV_PADLOCK 41 select CRYPTO_HASH 42 select CRYPTO_SHA1 43 select CRYPTO_SHA256 44 help 45 Use VIA PadLock for SHA1/SHA256 algorithms. 46 47 Available in VIA C7 and newer processors. 48 49 If unsure say M. The compiled module will be 50 called padlock-sha. 51 52config CRYPTO_DEV_GEODE 53 tristate "Support for the Geode LX AES engine" 54 depends on X86_32 && PCI 55 select CRYPTO_ALGAPI 56 select CRYPTO_BLKCIPHER 57 help 58 Say 'Y' here to use the AMD Geode LX processor on-board AES 59 engine for the CryptoAPI AES algorithm. 60 61 To compile this driver as a module, choose M here: the module 62 will be called geode-aes. 63 64config ZCRYPT 65 tristate "Support for PCI-attached cryptographic adapters" 66 depends on S390 67 select HW_RANDOM 68 help 69 Select this option if you want to use a PCI-attached cryptographic 70 adapter like: 71 + PCI Cryptographic Accelerator (PCICA) 72 + PCI Cryptographic Coprocessor (PCICC) 73 + PCI-X Cryptographic Coprocessor (PCIXCC) 74 + Crypto Express2 Coprocessor (CEX2C) 75 + Crypto Express2 Accelerator (CEX2A) 76 + Crypto Express3 Coprocessor (CEX3C) 77 + Crypto Express3 Accelerator (CEX3A) 78 79config CRYPTO_SHA1_S390 80 tristate "SHA1 digest algorithm" 81 depends on S390 82 select CRYPTO_HASH 83 help 84 This is the s390 hardware accelerated implementation of the 85 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2). 86 87 It is available as of z990. 88 89config CRYPTO_SHA256_S390 90 tristate "SHA256 digest algorithm" 91 depends on S390 92 select CRYPTO_HASH 93 help 94 This is the s390 hardware accelerated implementation of the 95 SHA256 secure hash standard (DFIPS 180-2). 96 97 It is available as of z9. 98 99config CRYPTO_SHA512_S390 100 tristate "SHA384 and SHA512 digest algorithm" 101 depends on S390 102 select CRYPTO_HASH 103 help 104 This is the s390 hardware accelerated implementation of the 105 SHA512 secure hash standard. 106 107 It is available as of z10. 108 109config CRYPTO_DES_S390 110 tristate "DES and Triple DES cipher algorithms" 111 depends on S390 112 select CRYPTO_ALGAPI 113 select CRYPTO_BLKCIPHER 114 select CRYPTO_DES 115 help 116 This is the s390 hardware accelerated implementation of the 117 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3). 118 119 As of z990 the ECB and CBC mode are hardware accelerated. 120 As of z196 the CTR mode is hardware accelerated. 121 122config CRYPTO_AES_S390 123 tristate "AES cipher algorithms" 124 depends on S390 125 select CRYPTO_ALGAPI 126 select CRYPTO_BLKCIPHER 127 help 128 This is the s390 hardware accelerated implementation of the 129 AES cipher algorithms (FIPS-197). 130 131 As of z9 the ECB and CBC modes are hardware accelerated 132 for 128 bit keys. 133 As of z10 the ECB and CBC modes are hardware accelerated 134 for all AES key sizes. 135 As of z196 the CTR mode is hardware accelerated for all AES 136 key sizes and XTS mode is hardware accelerated for 256 and 137 512 bit keys. 138 139config S390_PRNG 140 tristate "Pseudo random number generator device driver" 141 depends on S390 142 default "m" 143 help 144 Select this option if you want to use the s390 pseudo random number 145 generator. The PRNG is part of the cryptographic processor functions 146 and uses triple-DES to generate secure random numbers like the 147 ANSI X9.17 standard. User-space programs access the 148 pseudo-random-number device through the char device /dev/prandom. 149 150 It is available as of z9. 151 152config CRYPTO_GHASH_S390 153 tristate "GHASH digest algorithm" 154 depends on S390 155 select CRYPTO_HASH 156 help 157 This is the s390 hardware accelerated implementation of the 158 GHASH message digest algorithm for GCM (Galois/Counter Mode). 159 160 It is available as of z196. 161 162config CRYPTO_DEV_MV_CESA 163 tristate "Marvell's Cryptographic Engine" 164 depends on PLAT_ORION 165 select CRYPTO_ALGAPI 166 select CRYPTO_AES 167 select CRYPTO_BLKCIPHER2 168 select CRYPTO_HASH 169 help 170 This driver allows you to utilize the Cryptographic Engines and 171 Security Accelerator (CESA) which can be found on the Marvell Orion 172 and Kirkwood SoCs, such as QNAP's TS-209. 173 174 Currently the driver supports AES in ECB and CBC mode without DMA. 175 176config CRYPTO_DEV_NIAGARA2 177 tristate "Niagara2 Stream Processing Unit driver" 178 select CRYPTO_DES 179 select CRYPTO_ALGAPI 180 depends on SPARC64 181 help 182 Each core of a Niagara2 processor contains a Stream 183 Processing Unit, which itself contains several cryptographic 184 sub-units. One set provides the Modular Arithmetic Unit, 185 used for SSL offload. The other set provides the Cipher 186 Group, which can perform encryption, decryption, hashing, 187 checksumming, and raw copies. 188 189config CRYPTO_DEV_HIFN_795X 190 tristate "Driver HIFN 795x crypto accelerator chips" 191 select CRYPTO_DES 192 select CRYPTO_ALGAPI 193 select CRYPTO_BLKCIPHER 194 select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG 195 depends on PCI 196 depends on !ARCH_DMA_ADDR_T_64BIT 197 help 198 This option allows you to have support for HIFN 795x crypto adapters. 199 200config CRYPTO_DEV_HIFN_795X_RNG 201 bool "HIFN 795x random number generator" 202 depends on CRYPTO_DEV_HIFN_795X 203 help 204 Select this option if you want to enable the random number generator 205 on the HIFN 795x crypto adapters. 206 207source drivers/crypto/caam/Kconfig 208 209config CRYPTO_DEV_TALITOS 210 tristate "Talitos Freescale Security Engine (SEC)" 211 select CRYPTO_ALGAPI 212 select CRYPTO_AUTHENC 213 select HW_RANDOM 214 depends on FSL_SOC 215 help 216 Say 'Y' here to use the Freescale Security Engine (SEC) 217 to offload cryptographic algorithm computation. 218 219 The Freescale SEC is present on PowerQUICC 'E' processors, such 220 as the MPC8349E and MPC8548E. 221 222 To compile this driver as a module, choose M here: the module 223 will be called talitos. 224 225config CRYPTO_DEV_IXP4XX 226 tristate "Driver for IXP4xx crypto hardware acceleration" 227 depends on ARCH_IXP4XX 228 select CRYPTO_DES 229 select CRYPTO_ALGAPI 230 select CRYPTO_AUTHENC 231 select CRYPTO_BLKCIPHER 232 help 233 Driver for the IXP4xx NPE crypto engine. 234 235config CRYPTO_DEV_PPC4XX 236 tristate "Driver AMCC PPC4xx crypto accelerator" 237 depends on PPC && 4xx 238 select CRYPTO_HASH 239 select CRYPTO_ALGAPI 240 select CRYPTO_BLKCIPHER 241 help 242 This option allows you to have support for AMCC crypto acceleration. 243 244config CRYPTO_DEV_OMAP_SHAM 245 tristate "Support for OMAP SHA1/MD5 hw accelerator" 246 depends on ARCH_OMAP2 || ARCH_OMAP3 247 select CRYPTO_SHA1 248 select CRYPTO_MD5 249 help 250 OMAP processors have SHA1/MD5 hw accelerator. Select this if you 251 want to use the OMAP module for SHA1/MD5 algorithms. 252 253config CRYPTO_DEV_OMAP_AES 254 tristate "Support for OMAP AES hw engine" 255 depends on ARCH_OMAP2 || ARCH_OMAP3 256 select CRYPTO_AES 257 help 258 OMAP processors have AES module accelerator. Select this if you 259 want to use the OMAP module for AES algorithms. 260 261config CRYPTO_DEV_PICOXCELL 262 tristate "Support for picoXcell IPSEC and Layer2 crypto engines" 263 depends on ARCH_PICOXCELL && HAVE_CLK 264 select CRYPTO_AES 265 select CRYPTO_AUTHENC 266 select CRYPTO_ALGAPI 267 select CRYPTO_DES 268 select CRYPTO_CBC 269 select CRYPTO_ECB 270 select CRYPTO_SEQIV 271 help 272 This option enables support for the hardware offload engines in the 273 Picochip picoXcell SoC devices. Select this for IPSEC ESP offload 274 and for 3gpp Layer 2 ciphering support. 275 276 Saying m here will build a module named pipcoxcell_crypto. 277 278config CRYPTO_DEV_S5P 279 tristate "Support for Samsung S5PV210 crypto accelerator" 280 depends on ARCH_S5PV210 281 select CRYPTO_AES 282 select CRYPTO_ALGAPI 283 select CRYPTO_BLKCIPHER 284 help 285 This option allows you to have support for S5P crypto acceleration. 286 Select this to offload Samsung S5PV210 or S5PC110 from AES 287 algorithms execution. 288 289config CRYPTO_DEV_TEGRA_AES 290 tristate "Support for TEGRA AES hw engine" 291 depends on ARCH_TEGRA 292 select CRYPTO_AES 293 help 294 TEGRA processors have AES module accelerator. Select this if you 295 want to use the TEGRA module for AES algorithms. 296 297 To compile this driver as a module, choose M here: the module 298 will be called tegra-aes. 299 300config CRYPTO_DEV_NX 301 tristate "Support for Power7+ in-Nest cryptographic acceleration" 302 depends on PPC64 && IBMVIO 303 select CRYPTO_AES 304 select CRYPTO_CBC 305 select CRYPTO_ECB 306 select CRYPTO_CCM 307 select CRYPTO_GCM 308 select CRYPTO_AUTHENC 309 select CRYPTO_XCBC 310 select CRYPTO_SHA256 311 select CRYPTO_SHA512 312 help 313 Support for Power7+ in-Nest cryptographic acceleration. This 314 module supports acceleration for AES and SHA2 algorithms. If you 315 choose 'M' here, this module will be called nx_crypto. 316 317config CRYPTO_DEV_UX500 318 tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration" 319 depends on ARCH_U8500 320 select CRYPTO_ALGAPI 321 help 322 Driver for ST-Ericsson UX500 crypto engine. 323 324if CRYPTO_DEV_UX500 325 source "drivers/crypto/ux500/Kconfig" 326endif # if CRYPTO_DEV_UX500 327 328config CRYPTO_DEV_BFIN_CRC 329 tristate "Support for Blackfin CRC hardware" 330 depends on BF60x 331 help 332 Newer Blackfin processors have CRC hardware. Select this if you 333 want to use the Blackfin CRC module. 334 335config CRYPTO_DEV_ATMEL_AES 336 tristate "Support for Atmel AES hw accelerator" 337 depends on ARCH_AT91 338 select CRYPTO_CBC 339 select CRYPTO_ECB 340 select CRYPTO_AES 341 select CRYPTO_ALGAPI 342 select CRYPTO_BLKCIPHER 343 select CONFIG_AT_HDMAC 344 help 345 Some Atmel processors have AES hw accelerator. 346 Select this if you want to use the Atmel module for 347 AES algorithms. 348 349 To compile this driver as a module, choose M here: the module 350 will be called atmel-aes. 351 352config CRYPTO_DEV_ATMEL_TDES 353 tristate "Support for Atmel DES/TDES hw accelerator" 354 depends on ARCH_AT91 355 select CRYPTO_DES 356 select CRYPTO_CBC 357 select CRYPTO_ECB 358 select CRYPTO_ALGAPI 359 select CRYPTO_BLKCIPHER 360 help 361 Some Atmel processors have DES/TDES hw accelerator. 362 Select this if you want to use the Atmel module for 363 DES/TDES algorithms. 364 365 To compile this driver as a module, choose M here: the module 366 will be called atmel-tdes. 367 368config CRYPTO_DEV_ATMEL_SHA 369 tristate "Support for Atmel SHA1/SHA256 hw accelerator" 370 depends on ARCH_AT91 371 select CRYPTO_SHA1 372 select CRYPTO_SHA256 373 select CRYPTO_ALGAPI 374 help 375 Some Atmel processors have SHA1/SHA256 hw accelerator. 376 Select this if you want to use the Atmel module for 377 SHA1/SHA256 algorithms. 378 379 To compile this driver as a module, choose M here: the module 380 will be called atmel-sha. 381 382endif # CRYPTO_HW 383