drivers/crypto/Kconfig

   1 # SPDX-License-Identifier: GPL-2.0-only
   2
   3 menuconfig CRYPTO_HW
   4         bool "Hardware crypto devices"
   5         default y
   6         ---help---
   7           Say Y here to get to see options for hardware crypto devices and
   8           processors. This option alone does not add any kernel code.
   9
  10           If you say N, all options in this submenu will be skipped and disabled.
  11
  12 if CRYPTO_HW
  13
  14 config CRYPTO_DEV_PADLOCK
  15         tristate "Support for VIA PadLock ACE"
  16         depends on X86 && !UML
  17         help
  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.
  22
  23           The instructions are used only when the CPU supports them.
  24           Otherwise software encryption is used.
  25
  26 config CRYPTO_DEV_PADLOCK_AES
  27         tristate "PadLock driver for AES algorithm"
  28         depends on CRYPTO_DEV_PADLOCK
  29         select CRYPTO_BLKCIPHER
  30         select CRYPTO_AES
  31         help
  32           Use VIA PadLock for AES algorithm.
  33
  34           Available in VIA C3 and newer CPUs.
  35
  36           If unsure say M. The compiled module will be
  37           called padlock-aes.
  38
  39 config CRYPTO_DEV_PADLOCK_SHA
  40         tristate "PadLock driver for SHA1 and SHA256 algorithms"
  41         depends on CRYPTO_DEV_PADLOCK
  42         select CRYPTO_HASH
  43         select CRYPTO_SHA1
  44         select CRYPTO_SHA256
  45         help
  46           Use VIA PadLock for SHA1/SHA256 algorithms.
  47
  48           Available in VIA C7 and newer processors.
  49
  50           If unsure say M. The compiled module will be
  51           called padlock-sha.
  52
  53 config CRYPTO_DEV_GEODE
  54         tristate "Support for the Geode LX AES engine"
  55         depends on X86_32 && PCI
  56         select CRYPTO_ALGAPI
  57         select CRYPTO_BLKCIPHER
  58         help
  59           Say 'Y' here to use the AMD Geode LX processor on-board AES
  60           engine for the CryptoAPI AES algorithm.
  61
  62           To compile this driver as a module, choose M here: the module
  63           will be called geode-aes.
  64
  65 config ZCRYPT
  66         tristate "Support for s390 cryptographic adapters"
  67         depends on S390
  68         select HW_RANDOM
  69         help
  70           Select this option if you want to enable support for
  71           s390 cryptographic adapters like:
  72           + PCI-X Cryptographic Coprocessor (PCIXCC)
  73           + Crypto Express 2,3,4 or 5 Coprocessor (CEXxC)
  74           + Crypto Express 2,3,4 or 5 Accelerator (CEXxA)
  75           + Crypto Express 4 or 5 EP11 Coprocessor (CEXxP)
  76
  77 config ZCRYPT_MULTIDEVNODES
  78         bool "Support for multiple zcrypt device nodes"
  79         default y
  80         depends on S390
  81         depends on ZCRYPT
  82         help
  83           With this option enabled the zcrypt device driver can
  84           provide multiple devices nodes in /dev. Each device
  85           node can get customized to limit access and narrow
  86           down the use of the available crypto hardware.
  87
  88 config PKEY
  89         tristate "Kernel API for protected key handling"
  90         depends on S390
  91         depends on ZCRYPT
  92         help
  93           With this option enabled the pkey kernel module provides an API
  94           for creation and handling of protected keys. Other parts of the
  95           kernel or userspace applications may use these functions.
  96
  97           Select this option if you want to enable the kernel and userspace
  98           API for proteced key handling.
  99
 100           Please note that creation of protected keys from secure keys
 101           requires to have at least one CEX card in coprocessor mode
 102           available at runtime.
 103
 104 config CRYPTO_PAES_S390
 105         tristate "PAES cipher algorithms"
 106         depends on S390
 107         depends on ZCRYPT
 108         depends on PKEY
 109         select CRYPTO_ALGAPI
 110         select CRYPTO_BLKCIPHER
 111         help
 112           This is the s390 hardware accelerated implementation of the
 113           AES cipher algorithms for use with protected key.
 114
 115           Select this option if you want to use the paes cipher
 116           for example to use protected key encrypted devices.
 117
 118 config CRYPTO_SHA1_S390
 119         tristate "SHA1 digest algorithm"
 120         depends on S390
 121         select CRYPTO_HASH
 122         help
 123           This is the s390 hardware accelerated implementation of the
 124           SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
 125
 126           It is available as of z990.
 127
 128 config CRYPTO_SHA256_S390
 129         tristate "SHA256 digest algorithm"
 130         depends on S390
 131         select CRYPTO_HASH
 132         help
 133           This is the s390 hardware accelerated implementation of the
 134           SHA256 secure hash standard (DFIPS 180-2).
 135
 136           It is available as of z9.
 137
 138 config CRYPTO_SHA512_S390
 139         tristate "SHA384 and SHA512 digest algorithm"
 140         depends on S390
 141         select CRYPTO_HASH
 142         help
 143           This is the s390 hardware accelerated implementation of the
 144           SHA512 secure hash standard.
 145
 146           It is available as of z10.
 147
 148 config CRYPTO_DES_S390
 149         tristate "DES and Triple DES cipher algorithms"
 150         depends on S390
 151         select CRYPTO_ALGAPI
 152         select CRYPTO_BLKCIPHER
 153         select CRYPTO_DES
 154         help
 155           This is the s390 hardware accelerated implementation of the
 156           DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
 157
 158           As of z990 the ECB and CBC mode are hardware accelerated.
 159           As of z196 the CTR mode is hardware accelerated.
 160
 161 config CRYPTO_AES_S390
 162         tristate "AES cipher algorithms"
 163         depends on S390
 164         select CRYPTO_ALGAPI
 165         select CRYPTO_BLKCIPHER
 166         help
 167           This is the s390 hardware accelerated implementation of the
 168           AES cipher algorithms (FIPS-197).
 169
 170           As of z9 the ECB and CBC modes are hardware accelerated
 171           for 128 bit keys.
 172           As of z10 the ECB and CBC modes are hardware accelerated
 173           for all AES key sizes.
 174           As of z196 the CTR mode is hardware accelerated for all AES
 175           key sizes and XTS mode is hardware accelerated for 256 and
 176           512 bit keys.
 177
 178 config S390_PRNG
 179         tristate "Pseudo random number generator device driver"
 180         depends on S390
 181         default "m"
 182         help
 183           Select this option if you want to use the s390 pseudo random number
 184           generator. The PRNG is part of the cryptographic processor functions
 185           and uses triple-DES to generate secure random numbers like the
 186           ANSI X9.17 standard. User-space programs access the
 187           pseudo-random-number device through the char device /dev/prandom.
 188
 189           It is available as of z9.
 190
 191 config CRYPTO_GHASH_S390
 192         tristate "GHASH digest algorithm"
 193         depends on S390
 194         select CRYPTO_HASH
 195         help
 196           This is the s390 hardware accelerated implementation of the
 197           GHASH message digest algorithm for GCM (Galois/Counter Mode).
 198
 199           It is available as of z196.
 200
 201 config CRYPTO_CRC32_S390
 202         tristate "CRC-32 algorithms"
 203         depends on S390
 204         select CRYPTO_HASH
 205         select CRC32
 206         help
 207           Select this option if you want to use hardware accelerated
 208           implementations of CRC algorithms.  With this option, you
 209           can optimize the computation of CRC-32 (IEEE 802.3 Ethernet)
 210           and CRC-32C (Castagnoli).
 211
 212           It is available with IBM z13 or later.
 213
 214 config CRYPTO_DEV_MARVELL_CESA
 215         tristate "Marvell's Cryptographic Engine driver"
 216         depends on PLAT_ORION || ARCH_MVEBU
 217         select CRYPTO_AES
 218         select CRYPTO_DES
 219         select CRYPTO_BLKCIPHER
 220         select CRYPTO_HASH
 221         select SRAM
 222         help
 223           This driver allows you to utilize the Cryptographic Engines and
 224           Security Accelerator (CESA) which can be found on MVEBU and ORION
 225           platforms.
 226           This driver supports CPU offload through DMA transfers.
 227
 228 config CRYPTO_DEV_NIAGARA2
 229        tristate "Niagara2 Stream Processing Unit driver"
 230        select CRYPTO_DES
 231        select CRYPTO_BLKCIPHER
 232        select CRYPTO_HASH
 233        select CRYPTO_MD5
 234        select CRYPTO_SHA1
 235        select CRYPTO_SHA256
 236        depends on SPARC64
 237        help
 238           Each core of a Niagara2 processor contains a Stream
 239           Processing Unit, which itself contains several cryptographic
 240           sub-units.  One set provides the Modular Arithmetic Unit,
 241           used for SSL offload.  The other set provides the Cipher
 242           Group, which can perform encryption, decryption, hashing,
 243           checksumming, and raw copies.
 244
 245 config CRYPTO_DEV_HIFN_795X
 246         tristate "Driver HIFN 795x crypto accelerator chips"
 247         select CRYPTO_DES
 248         select CRYPTO_BLKCIPHER
 249         select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG
 250         depends on PCI
 251         depends on !ARCH_DMA_ADDR_T_64BIT
 252         help
 253           This option allows you to have support for HIFN 795x crypto adapters.
 254
 255 config CRYPTO_DEV_HIFN_795X_RNG
 256         bool "HIFN 795x random number generator"
 257         depends on CRYPTO_DEV_HIFN_795X
 258         help
 259           Select this option if you want to enable the random number generator
 260           on the HIFN 795x crypto adapters.
 261
 262 source "drivers/crypto/caam/Kconfig"
 263
 264 config CRYPTO_DEV_TALITOS
 265         tristate "Talitos Freescale Security Engine (SEC)"
 266         select CRYPTO_AEAD
 267         select CRYPTO_AUTHENC
 268         select CRYPTO_BLKCIPHER
 269         select CRYPTO_HASH
 270         select HW_RANDOM
 271         depends on FSL_SOC
 272         help
 273           Say 'Y' here to use the Freescale Security Engine (SEC)
 274           to offload cryptographic algorithm computation.
 275
 276           The Freescale SEC is present on PowerQUICC 'E' processors, such
 277           as the MPC8349E and MPC8548E.
 278
 279           To compile this driver as a module, choose M here: the module
 280           will be called talitos.
 281
 282 config CRYPTO_DEV_TALITOS1
 283         bool "SEC1 (SEC 1.0 and SEC Lite 1.2)"
 284         depends on CRYPTO_DEV_TALITOS
 285         depends on PPC_8xx || PPC_82xx
 286         default y
 287         help
 288           Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0
 289           found on MPC82xx or the Freescale Security Engine (SEC Lite)
 290           version 1.2 found on MPC8xx
 291
 292 config CRYPTO_DEV_TALITOS2
 293         bool "SEC2+ (SEC version 2.0 or upper)"
 294         depends on CRYPTO_DEV_TALITOS
 295         default y if !PPC_8xx
 296         help
 297           Say 'Y' here to use the Freescale Security Engine (SEC)
 298           version 2 and following as found on MPC83xx, MPC85xx, etc ...
 299
 300 config CRYPTO_DEV_IXP4XX
 301         tristate "Driver for IXP4xx crypto hardware acceleration"
 302         depends on ARCH_IXP4XX && IXP4XX_QMGR && IXP4XX_NPE
 303         select CRYPTO_DES
 304         select CRYPTO_AEAD
 305         select CRYPTO_AUTHENC
 306         select CRYPTO_BLKCIPHER
 307         help
 308           Driver for the IXP4xx NPE crypto engine.
 309
 310 config CRYPTO_DEV_PPC4XX
 311         tristate "Driver AMCC PPC4xx crypto accelerator"
 312         depends on PPC && 4xx
 313         select CRYPTO_HASH
 314         select CRYPTO_AEAD
 315         select CRYPTO_AES
 316         select CRYPTO_CCM
 317         select CRYPTO_CTR
 318         select CRYPTO_GCM
 319         select CRYPTO_BLKCIPHER
 320         help
 321           This option allows you to have support for AMCC crypto acceleration.
 322
 323 config HW_RANDOM_PPC4XX
 324         bool "PowerPC 4xx generic true random number generator support"
 325         depends on CRYPTO_DEV_PPC4XX && HW_RANDOM
 326         default y
 327         ---help---
 328          This option provides the kernel-side support for the TRNG hardware
 329          found in the security function of some PowerPC 4xx SoCs.
 330
 331 config CRYPTO_DEV_OMAP
 332         tristate "Support for OMAP crypto HW accelerators"
 333         depends on ARCH_OMAP2PLUS
 334         help
 335           OMAP processors have various crypto HW accelerators. Select this if
 336           you want to use the OMAP modules for any of the crypto algorithms.
 337
 338 if CRYPTO_DEV_OMAP
 339
 340 config CRYPTO_DEV_OMAP_SHAM
 341         tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator"
 342         depends on ARCH_OMAP2PLUS
 343         select CRYPTO_SHA1
 344         select CRYPTO_MD5
 345         select CRYPTO_SHA256
 346         select CRYPTO_SHA512
 347         select CRYPTO_HMAC
 348         help
 349           OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you
 350           want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
 351
 352 config CRYPTO_DEV_OMAP_AES
 353         tristate "Support for OMAP AES hw engine"
 354         depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS
 355         select CRYPTO_AES
 356         select CRYPTO_BLKCIPHER
 357         select CRYPTO_ENGINE
 358         select CRYPTO_CBC
 359         select CRYPTO_ECB
 360         select CRYPTO_CTR
 361         select CRYPTO_AEAD
 362         help
 363           OMAP processors have AES module accelerator. Select this if you
 364           want to use the OMAP module for AES algorithms.
 365
 366 config CRYPTO_DEV_OMAP_DES
 367         tristate "Support for OMAP DES/3DES hw engine"
 368         depends on ARCH_OMAP2PLUS
 369         select CRYPTO_DES
 370         select CRYPTO_BLKCIPHER
 371         select CRYPTO_ENGINE
 372         help
 373           OMAP processors have DES/3DES module accelerator. Select this if you
 374           want to use the OMAP module for DES and 3DES algorithms. Currently
 375           the ECB and CBC modes of operation are supported by the driver. Also
 376           accesses made on unaligned boundaries are supported.
 377
 378 endif # CRYPTO_DEV_OMAP
 379
 380 config CRYPTO_DEV_PICOXCELL
 381         tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
 382         depends on (ARCH_PICOXCELL || COMPILE_TEST) && HAVE_CLK
 383         select CRYPTO_AEAD
 384         select CRYPTO_AES
 385         select CRYPTO_AUTHENC
 386         select CRYPTO_BLKCIPHER
 387         select CRYPTO_DES
 388         select CRYPTO_CBC
 389         select CRYPTO_ECB
 390         select CRYPTO_SEQIV
 391         help
 392           This option enables support for the hardware offload engines in the
 393           Picochip picoXcell SoC devices. Select this for IPSEC ESP offload
 394           and for 3gpp Layer 2 ciphering support.
 395
 396           Saying m here will build a module named pipcoxcell_crypto.
 397
 398 config CRYPTO_DEV_SAHARA
 399         tristate "Support for SAHARA crypto accelerator"
 400         depends on ARCH_MXC && OF
 401         select CRYPTO_BLKCIPHER
 402         select CRYPTO_AES
 403         select CRYPTO_ECB
 404         help
 405           This option enables support for the SAHARA HW crypto accelerator
 406           found in some Freescale i.MX chips.
 407
 408 config CRYPTO_DEV_EXYNOS_RNG
 409         tristate "EXYNOS HW pseudo random number generator support"
 410         depends on ARCH_EXYNOS || COMPILE_TEST
 411         depends on HAS_IOMEM
 412         select CRYPTO_RNG
 413         ---help---
 414           This driver provides kernel-side support through the
 415           cryptographic API for the pseudo random number generator hardware
 416           found on Exynos SoCs.
 417
 418           To compile this driver as a module, choose M here: the
 419           module will be called exynos-rng.
 420
 421           If unsure, say Y.
 422
 423 config CRYPTO_DEV_S5P
 424         tristate "Support for Samsung S5PV210/Exynos crypto accelerator"
 425         depends on ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST
 426         depends on HAS_IOMEM
 427         select CRYPTO_AES
 428         select CRYPTO_BLKCIPHER
 429         help
 430           This option allows you to have support for S5P crypto acceleration.
 431           Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES
 432           algorithms execution.
 433
 434 config CRYPTO_DEV_EXYNOS_HASH
 435         bool "Support for Samsung Exynos HASH accelerator"
 436         depends on CRYPTO_DEV_S5P
 437         depends on !CRYPTO_DEV_EXYNOS_RNG && CRYPTO_DEV_EXYNOS_RNG!=m
 438         select CRYPTO_SHA1
 439         select CRYPTO_MD5
 440         select CRYPTO_SHA256
 441         help
 442           Select this to offload Exynos from HASH MD5/SHA1/SHA256.
 443           This will select software SHA1, MD5 and SHA256 as they are
 444           needed for small and zero-size messages.
 445           HASH algorithms will be disabled if EXYNOS_RNG
 446           is enabled due to hw conflict.
 447
 448 config CRYPTO_DEV_NX
 449         bool "Support for IBM PowerPC Nest (NX) cryptographic acceleration"
 450         depends on PPC64
 451         help
 452           This enables support for the NX hardware cryptographic accelerator
 453           coprocessor that is in IBM PowerPC P7+ or later processors.  This
 454           does not actually enable any drivers, it only allows you to select
 455           which acceleration type (encryption and/or compression) to enable.
 456
 457 if CRYPTO_DEV_NX
 458         source "drivers/crypto/nx/Kconfig"
 459 endif
 460
 461 config CRYPTO_DEV_UX500
 462         tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration"
 463         depends on ARCH_U8500
 464         help
 465           Driver for ST-Ericsson UX500 crypto engine.
 466
 467 if CRYPTO_DEV_UX500
 468         source "drivers/crypto/ux500/Kconfig"
 469 endif # if CRYPTO_DEV_UX500
 470
 471 config CRYPTO_DEV_ATMEL_AUTHENC
 472         tristate "Support for Atmel IPSEC/SSL hw accelerator"
 473         depends on ARCH_AT91 || COMPILE_TEST
 474         select CRYPTO_AUTHENC
 475         select CRYPTO_DEV_ATMEL_AES
 476         select CRYPTO_DEV_ATMEL_SHA
 477         help
 478           Some Atmel processors can combine the AES and SHA hw accelerators
 479           to enhance support of IPSEC/SSL.
 480           Select this if you want to use the Atmel modules for
 481           authenc(hmac(shaX),Y(cbc)) algorithms.
 482
 483 config CRYPTO_DEV_ATMEL_AES
 484         tristate "Support for Atmel AES hw accelerator"
 485         depends on ARCH_AT91 || COMPILE_TEST
 486         select CRYPTO_AES
 487         select CRYPTO_AEAD
 488         select CRYPTO_BLKCIPHER
 489         help
 490           Some Atmel processors have AES hw accelerator.
 491           Select this if you want to use the Atmel module for
 492           AES algorithms.
 493
 494           To compile this driver as a module, choose M here: the module
 495           will be called atmel-aes.
 496
 497 config CRYPTO_DEV_ATMEL_TDES
 498         tristate "Support for Atmel DES/TDES hw accelerator"
 499         depends on ARCH_AT91 || COMPILE_TEST
 500         select CRYPTO_DES
 501         select CRYPTO_BLKCIPHER
 502         help
 503           Some Atmel processors have DES/TDES hw accelerator.
 504           Select this if you want to use the Atmel module for
 505           DES/TDES algorithms.
 506
 507           To compile this driver as a module, choose M here: the module
 508           will be called atmel-tdes.
 509
 510 config CRYPTO_DEV_ATMEL_SHA
 511         tristate "Support for Atmel SHA hw accelerator"
 512         depends on ARCH_AT91 || COMPILE_TEST
 513         select CRYPTO_HASH
 514         help
 515           Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
 516           hw accelerator.
 517           Select this if you want to use the Atmel module for
 518           SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
 519
 520           To compile this driver as a module, choose M here: the module
 521           will be called atmel-sha.
 522
 523 config CRYPTO_DEV_ATMEL_I2C
 524         tristate
 525
 526 config CRYPTO_DEV_ATMEL_ECC
 527         tristate "Support for Microchip / Atmel ECC hw accelerator"
 528         depends on I2C
 529         select CRYPTO_DEV_ATMEL_I2C
 530         select CRYPTO_ECDH
 531         select CRC16
 532         help
 533           Microhip / Atmel ECC hw accelerator.
 534           Select this if you want to use the Microchip / Atmel module for
 535           ECDH algorithm.
 536
 537           To compile this driver as a module, choose M here: the module
 538           will be called atmel-ecc.
 539
 540 config CRYPTO_DEV_ATMEL_SHA204A
 541         tristate "Support for Microchip / Atmel SHA accelerator and RNG"
 542         depends on I2C
 543         select CRYPTO_DEV_ATMEL_I2C
 544         select HW_RANDOM
 545         select CRC16
 546         help
 547           Microhip / Atmel SHA accelerator and RNG.
 548           Select this if you want to use the Microchip / Atmel SHA204A
 549           module as a random number generator. (Other functions of the
 550           chip are currently not exposed by this driver)
 551
 552           To compile this driver as a module, choose M here: the module
 553           will be called atmel-sha204a.
 554
 555 config CRYPTO_DEV_CCP
 556         bool "Support for AMD Secure Processor"
 557         depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM
 558         help
 559           The AMD Secure Processor provides support for the Cryptographic Coprocessor
 560           (CCP) and the Platform Security Processor (PSP) devices.
 561
 562 if CRYPTO_DEV_CCP
 563         source "drivers/crypto/ccp/Kconfig"
 564 endif
 565
 566 config CRYPTO_DEV_MXS_DCP
 567         tristate "Support for Freescale MXS DCP"
 568         depends on (ARCH_MXS || ARCH_MXC)
 569         select STMP_DEVICE
 570         select CRYPTO_CBC
 571         select CRYPTO_ECB
 572         select CRYPTO_AES
 573         select CRYPTO_BLKCIPHER
 574         select CRYPTO_HASH
 575         help
 576           The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB
 577           co-processor on the die.
 578
 579           To compile this driver as a module, choose M here: the module
 580           will be called mxs-dcp.
 581
 582 source "drivers/crypto/qat/Kconfig"
 583 source "drivers/crypto/cavium/cpt/Kconfig"
 584 source "drivers/crypto/cavium/nitrox/Kconfig"
 585
 586 config CRYPTO_DEV_CAVIUM_ZIP
 587         tristate "Cavium ZIP driver"
 588         depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
 589         ---help---
 590           Select this option if you want to enable compression/decompression
 591           acceleration on Cavium's ARM based SoCs
 592
 593 config CRYPTO_DEV_QCE
 594         tristate "Qualcomm crypto engine accelerator"
 595         depends on ARCH_QCOM || COMPILE_TEST
 596         depends on HAS_IOMEM
 597         select CRYPTO_AES
 598         select CRYPTO_DES
 599         select CRYPTO_ECB
 600         select CRYPTO_CBC
 601         select CRYPTO_XTS
 602         select CRYPTO_CTR
 603         select CRYPTO_BLKCIPHER
 604         help
 605           This driver supports Qualcomm crypto engine accelerator
 606           hardware. To compile this driver as a module, choose M here. The
 607           module will be called qcrypto.
 608
 609 config CRYPTO_DEV_QCOM_RNG
 610         tristate "Qualcomm Random Number Generator Driver"
 611         depends on ARCH_QCOM || COMPILE_TEST
 612         select CRYPTO_RNG
 613         help
 614           This driver provides support for the Random Number
 615           Generator hardware found on Qualcomm SoCs.
 616
 617           To compile this driver as a module, choose M here. The
 618           module will be called qcom-rng. If unsure, say N.
 619
 620 config CRYPTO_DEV_VMX
 621         bool "Support for VMX cryptographic acceleration instructions"
 622         depends on PPC64 && VSX
 623         help
 624           Support for VMX cryptographic acceleration instructions.
 625
 626 source "drivers/crypto/vmx/Kconfig"
 627
 628 config CRYPTO_DEV_IMGTEC_HASH
 629         tristate "Imagination Technologies hardware hash accelerator"
 630         depends on MIPS || COMPILE_TEST
 631         select CRYPTO_MD5
 632         select CRYPTO_SHA1
 633         select CRYPTO_SHA256
 634         select CRYPTO_HASH
 635         help
 636           This driver interfaces with the Imagination Technologies
 637           hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256
 638           hashing algorithms.
 639
 640 config CRYPTO_DEV_SUN4I_SS
 641         tristate "Support for Allwinner Security System cryptographic accelerator"
 642         depends on ARCH_SUNXI && !64BIT
 643         select CRYPTO_MD5
 644         select CRYPTO_SHA1
 645         select CRYPTO_AES
 646         select CRYPTO_DES
 647         select CRYPTO_BLKCIPHER
 648         help
 649           Some Allwinner SoC have a crypto accelerator named
 650           Security System. Select this if you want to use it.
 651           The Security System handle AES/DES/3DES ciphers in CBC mode
 652           and SHA1 and MD5 hash algorithms.
 653
 654           To compile this driver as a module, choose M here: the module
 655           will be called sun4i-ss.
 656
 657 config CRYPTO_DEV_SUN4I_SS_PRNG
 658         bool "Support for Allwinner Security System PRNG"
 659         depends on CRYPTO_DEV_SUN4I_SS
 660         select CRYPTO_RNG
 661         help
 662           Select this option if you want to provide kernel-side support for
 663           the Pseudo-Random Number Generator found in the Security System.
 664
 665 config CRYPTO_DEV_ROCKCHIP
 666         tristate "Rockchip's Cryptographic Engine driver"
 667         depends on OF && ARCH_ROCKCHIP
 668         select CRYPTO_AES
 669         select CRYPTO_DES
 670         select CRYPTO_MD5
 671         select CRYPTO_SHA1
 672         select CRYPTO_SHA256
 673         select CRYPTO_HASH
 674         select CRYPTO_BLKCIPHER
 675
 676         help
 677           This driver interfaces with the hardware crypto accelerator.
 678           Supporting cbc/ecb chainmode, and aes/des/des3_ede cipher mode.
 679
 680 config CRYPTO_DEV_MEDIATEK
 681         tristate "MediaTek's EIP97 Cryptographic Engine driver"
 682         depends on (ARM && ARCH_MEDIATEK) || COMPILE_TEST
 683         select CRYPTO_AES
 684         select CRYPTO_AEAD
 685         select CRYPTO_BLKCIPHER
 686         select CRYPTO_CTR
 687         select CRYPTO_SHA1
 688         select CRYPTO_SHA256
 689         select CRYPTO_SHA512
 690         select CRYPTO_HMAC
 691         help
 692           This driver allows you to utilize the hardware crypto accelerator
 693           EIP97 which can be found on the MT7623 MT2701, MT8521p, etc ....
 694           Select this if you want to use it for AES/SHA1/SHA2 algorithms.
 695
 696 source "drivers/crypto/chelsio/Kconfig"
 697
 698 source "drivers/crypto/virtio/Kconfig"
 699
 700 config CRYPTO_DEV_BCM_SPU
 701         tristate "Broadcom symmetric crypto/hash acceleration support"
 702         depends on ARCH_BCM_IPROC
 703         depends on MAILBOX
 704         default m
 705         select CRYPTO_AUTHENC
 706         select CRYPTO_DES
 707         select CRYPTO_MD5
 708         select CRYPTO_SHA1
 709         select CRYPTO_SHA256
 710         select CRYPTO_SHA512
 711         help
 712           This driver provides support for Broadcom crypto acceleration using the
 713           Secure Processing Unit (SPU). The SPU driver registers ablkcipher,
 714           ahash, and aead algorithms with the kernel cryptographic API.
 715
 716 source "drivers/crypto/stm32/Kconfig"
 717
 718 config CRYPTO_DEV_SAFEXCEL
 719         tristate "Inside Secure's SafeXcel cryptographic engine driver"
 720         depends on OF
 721         depends on (ARM64 && ARCH_MVEBU) || (COMPILE_TEST && 64BIT)
 722         select CRYPTO_AES
 723         select CRYPTO_AUTHENC
 724         select CRYPTO_BLKCIPHER
 725         select CRYPTO_DES
 726         select CRYPTO_HASH
 727         select CRYPTO_HMAC
 728         select CRYPTO_MD5
 729         select CRYPTO_SHA1
 730         select CRYPTO_SHA256
 731         select CRYPTO_SHA512
 732         help
 733           This driver interfaces with the SafeXcel EIP-197 cryptographic engine
 734           designed by Inside Secure. Select this if you want to use CBC/ECB
 735           chain mode, AES cipher mode and SHA1/SHA224/SHA256/SHA512 hash
 736           algorithms.
 737
 738 config CRYPTO_DEV_ARTPEC6
 739         tristate "Support for Axis ARTPEC-6/7 hardware crypto acceleration."
 740         depends on ARM && (ARCH_ARTPEC || COMPILE_TEST)
 741         depends on OF
 742         select CRYPTO_AEAD
 743         select CRYPTO_AES
 744         select CRYPTO_ALGAPI
 745         select CRYPTO_BLKCIPHER
 746         select CRYPTO_CTR
 747         select CRYPTO_HASH
 748         select CRYPTO_SHA1
 749         select CRYPTO_SHA256
 750         select CRYPTO_SHA512
 751         help
 752           Enables the driver for the on-chip crypto accelerator
 753           of Axis ARTPEC SoCs.
 754
 755           To compile this driver as a module, choose M here.
 756
 757 config CRYPTO_DEV_CCREE
 758         tristate "Support for ARM TrustZone CryptoCell family of security processors"
 759         depends on CRYPTO && CRYPTO_HW && OF && HAS_DMA
 760         default n
 761         select CRYPTO_HASH
 762         select CRYPTO_BLKCIPHER
 763         select CRYPTO_DES
 764         select CRYPTO_AEAD
 765         select CRYPTO_AUTHENC
 766         select CRYPTO_SHA1
 767         select CRYPTO_MD5
 768         select CRYPTO_SHA256
 769         select CRYPTO_SHA512
 770         select CRYPTO_HMAC
 771         select CRYPTO_AES
 772         select CRYPTO_CBC
 773         select CRYPTO_ECB
 774         select CRYPTO_CTR
 775         select CRYPTO_XTS
 776         select CRYPTO_SM4
 777         select CRYPTO_SM3
 778         help
 779           Say 'Y' to enable a driver for the REE interface of the Arm
 780           TrustZone CryptoCell family of processors. Currently the
 781           CryptoCell 713, 703, 712, 710 and 630 are supported.
 782           Choose this if you wish to use hardware acceleration of
 783           cryptographic operations on the system REE.
 784           If unsure say Y.
 785
 786 source "drivers/crypto/hisilicon/Kconfig"
 787
 788 endif # CRYPTO_HW