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_AES 166 select CRYPTO_BLKCIPHER 167 select CRYPTO_HASH 168 select SRAM 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_BLKCIPHER 180 select CRYPTO_HASH 181 depends on SPARC64 182 help 183 Each core of a Niagara2 processor contains a Stream 184 Processing Unit, which itself contains several cryptographic 185 sub-units. One set provides the Modular Arithmetic Unit, 186 used for SSL offload. The other set provides the Cipher 187 Group, which can perform encryption, decryption, hashing, 188 checksumming, and raw copies. 189 190config CRYPTO_DEV_HIFN_795X 191 tristate "Driver HIFN 795x crypto accelerator chips" 192 select CRYPTO_DES 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_AEAD 212 select CRYPTO_AUTHENC 213 select CRYPTO_BLKCIPHER 214 select CRYPTO_HASH 215 select HW_RANDOM 216 depends on FSL_SOC 217 help 218 Say 'Y' here to use the Freescale Security Engine (SEC) 219 to offload cryptographic algorithm computation. 220 221 The Freescale SEC is present on PowerQUICC 'E' processors, such 222 as the MPC8349E and MPC8548E. 223 224 To compile this driver as a module, choose M here: the module 225 will be called talitos. 226 227config CRYPTO_DEV_TALITOS1 228 bool "SEC1 (SEC 1.0 and SEC Lite 1.2)" 229 depends on CRYPTO_DEV_TALITOS 230 depends on PPC_8xx || PPC_82xx 231 default y 232 help 233 Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0 234 found on MPC82xx or the Freescale Security Engine (SEC Lite) 235 version 1.2 found on MPC8xx 236 237config CRYPTO_DEV_TALITOS2 238 bool "SEC2+ (SEC version 2.0 or upper)" 239 depends on CRYPTO_DEV_TALITOS 240 default y if !PPC_8xx 241 help 242 Say 'Y' here to use the Freescale Security Engine (SEC) 243 version 2 and following as found on MPC83xx, MPC85xx, etc ... 244 245config CRYPTO_DEV_IXP4XX 246 tristate "Driver for IXP4xx crypto hardware acceleration" 247 depends on ARCH_IXP4XX && IXP4XX_QMGR && IXP4XX_NPE 248 select CRYPTO_DES 249 select CRYPTO_AEAD 250 select CRYPTO_AUTHENC 251 select CRYPTO_BLKCIPHER 252 help 253 Driver for the IXP4xx NPE crypto engine. 254 255config CRYPTO_DEV_PPC4XX 256 tristate "Driver AMCC PPC4xx crypto accelerator" 257 depends on PPC && 4xx 258 select CRYPTO_HASH 259 select CRYPTO_BLKCIPHER 260 help 261 This option allows you to have support for AMCC crypto acceleration. 262 263config CRYPTO_DEV_OMAP_SHAM 264 tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator" 265 depends on ARCH_OMAP2PLUS 266 select CRYPTO_SHA1 267 select CRYPTO_MD5 268 select CRYPTO_SHA256 269 select CRYPTO_SHA512 270 select CRYPTO_HMAC 271 help 272 OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you 273 want to use the OMAP module for MD5/SHA1/SHA2 algorithms. 274 275config CRYPTO_DEV_OMAP_AES 276 tristate "Support for OMAP AES hw engine" 277 depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS 278 select CRYPTO_AES 279 select CRYPTO_BLKCIPHER 280 help 281 OMAP processors have AES module accelerator. Select this if you 282 want to use the OMAP module for AES algorithms. 283 284config CRYPTO_DEV_OMAP_DES 285 tristate "Support for OMAP DES3DES hw engine" 286 depends on ARCH_OMAP2PLUS 287 select CRYPTO_DES 288 select CRYPTO_BLKCIPHER 289 help 290 OMAP processors have DES/3DES module accelerator. Select this if you 291 want to use the OMAP module for DES and 3DES algorithms. Currently 292 the ECB and CBC modes of operation supported by the driver. Also 293 accesses made on unaligned boundaries are also supported. 294 295config CRYPTO_DEV_PICOXCELL 296 tristate "Support for picoXcell IPSEC and Layer2 crypto engines" 297 depends on ARCH_PICOXCELL && HAVE_CLK 298 select CRYPTO_AEAD 299 select CRYPTO_AES 300 select CRYPTO_AUTHENC 301 select CRYPTO_BLKCIPHER 302 select CRYPTO_DES 303 select CRYPTO_CBC 304 select CRYPTO_ECB 305 select CRYPTO_SEQIV 306 help 307 This option enables support for the hardware offload engines in the 308 Picochip picoXcell SoC devices. Select this for IPSEC ESP offload 309 and for 3gpp Layer 2 ciphering support. 310 311 Saying m here will build a module named pipcoxcell_crypto. 312 313config CRYPTO_DEV_SAHARA 314 tristate "Support for SAHARA crypto accelerator" 315 depends on ARCH_MXC && OF 316 select CRYPTO_BLKCIPHER 317 select CRYPTO_AES 318 select CRYPTO_ECB 319 help 320 This option enables support for the SAHARA HW crypto accelerator 321 found in some Freescale i.MX chips. 322 323config CRYPTO_DEV_S5P 324 tristate "Support for Samsung S5PV210/Exynos crypto accelerator" 325 depends on ARCH_S5PV210 || ARCH_EXYNOS 326 select CRYPTO_AES 327 select CRYPTO_BLKCIPHER 328 help 329 This option allows you to have support for S5P crypto acceleration. 330 Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES 331 algorithms execution. 332 333config CRYPTO_DEV_NX 334 bool "Support for IBM PowerPC Nest (NX) cryptographic acceleration" 335 depends on PPC64 336 help 337 This enables support for the NX hardware cryptographic accelerator 338 coprocessor that is in IBM PowerPC P7+ or later processors. This 339 does not actually enable any drivers, it only allows you to select 340 which acceleration type (encryption and/or compression) to enable. 341 342if CRYPTO_DEV_NX 343 source "drivers/crypto/nx/Kconfig" 344endif 345 346config CRYPTO_DEV_UX500 347 tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration" 348 depends on ARCH_U8500 349 help 350 Driver for ST-Ericsson UX500 crypto engine. 351 352if CRYPTO_DEV_UX500 353 source "drivers/crypto/ux500/Kconfig" 354endif # if CRYPTO_DEV_UX500 355 356config CRYPTO_DEV_BFIN_CRC 357 tristate "Support for Blackfin CRC hardware" 358 depends on BF60x 359 help 360 Newer Blackfin processors have CRC hardware. Select this if you 361 want to use the Blackfin CRC module. 362 363config CRYPTO_DEV_ATMEL_AES 364 tristate "Support for Atmel AES hw accelerator" 365 depends on ARCH_AT91 366 select CRYPTO_AES 367 select CRYPTO_BLKCIPHER 368 select AT_HDMAC 369 help 370 Some Atmel processors have AES hw accelerator. 371 Select this if you want to use the Atmel module for 372 AES algorithms. 373 374 To compile this driver as a module, choose M here: the module 375 will be called atmel-aes. 376 377config CRYPTO_DEV_ATMEL_TDES 378 tristate "Support for Atmel DES/TDES hw accelerator" 379 depends on ARCH_AT91 380 select CRYPTO_DES 381 select CRYPTO_BLKCIPHER 382 help 383 Some Atmel processors have DES/TDES hw accelerator. 384 Select this if you want to use the Atmel module for 385 DES/TDES algorithms. 386 387 To compile this driver as a module, choose M here: the module 388 will be called atmel-tdes. 389 390config CRYPTO_DEV_ATMEL_SHA 391 tristate "Support for Atmel SHA hw accelerator" 392 depends on ARCH_AT91 393 select CRYPTO_HASH 394 help 395 Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512 396 hw accelerator. 397 Select this if you want to use the Atmel module for 398 SHA1/SHA224/SHA256/SHA384/SHA512 algorithms. 399 400 To compile this driver as a module, choose M here: the module 401 will be called atmel-sha. 402 403config CRYPTO_DEV_CCP 404 bool "Support for AMD Cryptographic Coprocessor" 405 depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM 406 help 407 The AMD Cryptographic Coprocessor provides hardware support 408 for encryption, hashing and related operations. 409 410if CRYPTO_DEV_CCP 411 source "drivers/crypto/ccp/Kconfig" 412endif 413 414config CRYPTO_DEV_MXS_DCP 415 tristate "Support for Freescale MXS DCP" 416 depends on ARCH_MXS 417 select CRYPTO_CBC 418 select CRYPTO_ECB 419 select CRYPTO_AES 420 select CRYPTO_BLKCIPHER 421 select CRYPTO_HASH 422 help 423 The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB 424 co-processor on the die. 425 426 To compile this driver as a module, choose M here: the module 427 will be called mxs-dcp. 428 429source "drivers/crypto/qat/Kconfig" 430 431config CRYPTO_DEV_QCE 432 tristate "Qualcomm crypto engine accelerator" 433 depends on (ARCH_QCOM || COMPILE_TEST) && HAS_DMA && HAS_IOMEM 434 select CRYPTO_AES 435 select CRYPTO_DES 436 select CRYPTO_ECB 437 select CRYPTO_CBC 438 select CRYPTO_XTS 439 select CRYPTO_CTR 440 select CRYPTO_BLKCIPHER 441 help 442 This driver supports Qualcomm crypto engine accelerator 443 hardware. To compile this driver as a module, choose M here. The 444 module will be called qcrypto. 445 446config CRYPTO_DEV_VMX 447 bool "Support for VMX cryptographic acceleration instructions" 448 depends on PPC64 449 help 450 Support for VMX cryptographic acceleration instructions. 451 452source "drivers/crypto/vmx/Kconfig" 453 454config CRYPTO_DEV_IMGTEC_HASH 455 tristate "Imagination Technologies hardware hash accelerator" 456 depends on MIPS || COMPILE_TEST 457 depends on HAS_DMA 458 select CRYPTO_MD5 459 select CRYPTO_SHA1 460 select CRYPTO_SHA256 461 select CRYPTO_HASH 462 help 463 This driver interfaces with the Imagination Technologies 464 hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256 465 hashing algorithms. 466 467endif # CRYPTO_HW 468