drivers/crypto/Kconfig

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