Kconfig 16.9 KB
Newer Older
1 2 3 4

menuconfig CRYPTO_HW
	bool "Hardware crypto devices"
	default y
5 6 7 8 9
	---help---
	  Say Y here to get to see options for hardware crypto devices and
	  processors. This option alone does not add any kernel code.

	  If you say N, all options in this submenu will be skipped and disabled.
10 11

if CRYPTO_HW
L
Linus Torvalds 已提交
12 13

config CRYPTO_DEV_PADLOCK
14
	tristate "Support for VIA PadLock ACE"
15
	depends on X86 && !UML
L
Linus Torvalds 已提交
16 17 18
	help
	  Some VIA processors come with an integrated crypto engine
	  (so called VIA PadLock ACE, Advanced Cryptography Engine)
19 20
	  that provides instructions for very fast cryptographic
	  operations with supported algorithms.
L
Linus Torvalds 已提交
21 22
	  
	  The instructions are used only when the CPU supports them.
23 24
	  Otherwise software encryption is used.

L
Linus Torvalds 已提交
25
config CRYPTO_DEV_PADLOCK_AES
26
	tristate "PadLock driver for AES algorithm"
L
Linus Torvalds 已提交
27
	depends on CRYPTO_DEV_PADLOCK
28
	select CRYPTO_BLKCIPHER
29
	select CRYPTO_AES
L
Linus Torvalds 已提交
30 31 32
	help
	  Use VIA PadLock for AES algorithm.

33 34 35
	  Available in VIA C3 and newer CPUs.

	  If unsure say M. The compiled module will be
36
	  called padlock-aes.
37

38 39 40
config CRYPTO_DEV_PADLOCK_SHA
	tristate "PadLock driver for SHA1 and SHA256 algorithms"
	depends on CRYPTO_DEV_PADLOCK
41
	select CRYPTO_HASH
42 43 44 45 46 47 48 49
	select CRYPTO_SHA1
	select CRYPTO_SHA256
	help
	  Use VIA PadLock for SHA1/SHA256 algorithms.

	  Available in VIA C7 and newer processors.

	  If unsure say M. The compiled module will be
50
	  called padlock-sha.
51

52 53
config CRYPTO_DEV_GEODE
	tristate "Support for the Geode LX AES engine"
54
	depends on X86_32 && PCI
55 56 57 58
	select CRYPTO_ALGAPI
	select CRYPTO_BLKCIPHER
	help
	  Say 'Y' here to use the AMD Geode LX processor on-board AES
59
	  engine for the CryptoAPI AES algorithm.
60 61 62 63

	  To compile this driver as a module, choose M here: the module
	  will be called geode-aes.

64 65 66
config ZCRYPT
	tristate "Support for PCI-attached cryptographic adapters"
	depends on S390
67
	select HW_RANDOM
68 69 70 71 72 73 74 75
	help
	  Select this option if you want to use a PCI-attached cryptographic
	  adapter like:
	  + PCI Cryptographic Accelerator (PCICA)
	  + PCI Cryptographic Coprocessor (PCICC)
	  + PCI-X Cryptographic Coprocessor (PCIXCC)
	  + Crypto Express2 Coprocessor (CEX2C)
	  + Crypto Express2 Accelerator (CEX2A)
76 77
	  + Crypto Express3 Coprocessor (CEX3C)
	  + Crypto Express3 Accelerator (CEX3A)
78

79 80 81
config CRYPTO_SHA1_S390
	tristate "SHA1 digest algorithm"
	depends on S390
H
Herbert Xu 已提交
82
	select CRYPTO_HASH
83 84 85 86
	help
	  This is the s390 hardware accelerated implementation of the
	  SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).

87 88
	  It is available as of z990.

89 90 91
config CRYPTO_SHA256_S390
	tristate "SHA256 digest algorithm"
	depends on S390
H
Herbert Xu 已提交
92
	select CRYPTO_HASH
93 94 95 96
	help
	  This is the s390 hardware accelerated implementation of the
	  SHA256 secure hash standard (DFIPS 180-2).

97
	  It is available as of z9.
98

99
config CRYPTO_SHA512_S390
100
	tristate "SHA384 and SHA512 digest algorithm"
101
	depends on S390
H
Herbert Xu 已提交
102
	select CRYPTO_HASH
103 104 105 106
	help
	  This is the s390 hardware accelerated implementation of the
	  SHA512 secure hash standard.

107
	  It is available as of z10.
108

109 110 111 112 113
config CRYPTO_DES_S390
	tristate "DES and Triple DES cipher algorithms"
	depends on S390
	select CRYPTO_ALGAPI
	select CRYPTO_BLKCIPHER
114
	select CRYPTO_DES
115
	help
116
	  This is the s390 hardware accelerated implementation of the
117 118
	  DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).

119 120 121
	  As of z990 the ECB and CBC mode are hardware accelerated.
	  As of z196 the CTR mode is hardware accelerated.

122 123 124 125 126 127 128
config CRYPTO_AES_S390
	tristate "AES cipher algorithms"
	depends on S390
	select CRYPTO_ALGAPI
	select CRYPTO_BLKCIPHER
	help
	  This is the s390 hardware accelerated implementation of the
129 130 131 132 133 134
	  AES cipher algorithms (FIPS-197).

	  As of z9 the ECB and CBC modes are hardware accelerated
	  for 128 bit keys.
	  As of z10 the ECB and CBC modes are hardware accelerated
	  for all AES key sizes.
135 136
	  As of z196 the CTR mode is hardware accelerated for all AES
	  key sizes and XTS mode is hardware accelerated for 256 and
137
	  512 bit keys.
138 139 140 141 142 143 144 145 146

config S390_PRNG
	tristate "Pseudo random number generator device driver"
	depends on S390
	default "m"
	help
	  Select this option if you want to use the s390 pseudo random number
	  generator. The PRNG is part of the cryptographic processor functions
	  and uses triple-DES to generate secure random numbers like the
147 148 149 150
	  ANSI X9.17 standard. User-space programs access the
	  pseudo-random-number device through the char device /dev/prandom.

	  It is available as of z9.
151

152 153 154 155 156 157 158 159 160 161
config CRYPTO_GHASH_S390
	tristate "GHASH digest algorithm"
	depends on S390
	select CRYPTO_HASH
	help
	  This is the s390 hardware accelerated implementation of the
	  GHASH message digest algorithm for GCM (Galois/Counter Mode).

	  It is available as of z196.

162 163 164 165 166 167 168 169 170 171 172 173 174
config CRYPTO_CRC32_S390
	tristate "CRC-32 algorithms"
	depends on S390
	select CRYPTO_HASH
	select CRC32
	help
	  Select this option if you want to use hardware accelerated
	  implementations of CRC algorithms.  With this option, you
	  can optimize the computation of CRC-32 (IEEE 802.3 Ethernet)
	  and CRC-32C (Castagnoli).

	  It is available with IBM z13 or later.

175 176 177 178
config CRYPTO_DEV_MV_CESA
	tristate "Marvell's Cryptographic Engine"
	depends on PLAT_ORION
	select CRYPTO_AES
179
	select CRYPTO_BLKCIPHER
180
	select CRYPTO_HASH
181
	select SRAM
182 183 184 185 186 187 188
	help
	  This driver allows you to utilize the Cryptographic Engines and
	  Security Accelerator (CESA) which can be found on the Marvell Orion
	  and Kirkwood SoCs, such as QNAP's TS-209.

	  Currently the driver supports AES in ECB and CBC mode without DMA.

189 190
config CRYPTO_DEV_MARVELL_CESA
	tristate "New Marvell's Cryptographic Engine driver"
191
	depends on PLAT_ORION || ARCH_MVEBU
192 193 194 195 196 197 198 199
	select CRYPTO_AES
	select CRYPTO_DES
	select CRYPTO_BLKCIPHER
	select CRYPTO_HASH
	select SRAM
	help
	  This driver allows you to utilize the Cryptographic Engines and
	  Security Accelerator (CESA) which can be found on the Armada 370.
200
	  This driver supports CPU offload through DMA transfers.
201 202 203 204

	  This driver is aimed at replacing the mv_cesa driver. This will only
	  happen once it has received proper testing.

205 206
config CRYPTO_DEV_NIAGARA2
       tristate "Niagara2 Stream Processing Unit driver"
207
       select CRYPTO_DES
208 209
       select CRYPTO_BLKCIPHER
       select CRYPTO_HASH
210 211 212
       select CRYPTO_MD5
       select CRYPTO_SHA1
       select CRYPTO_SHA256
213 214 215 216 217 218 219 220 221
       depends on SPARC64
       help
	  Each core of a Niagara2 processor contains a Stream
	  Processing Unit, which itself contains several cryptographic
	  sub-units.  One set provides the Modular Arithmetic Unit,
	  used for SSL offload.  The other set provides the Cipher
	  Group, which can perform encryption, decryption, hashing,
	  checksumming, and raw copies.

222 223
config CRYPTO_DEV_HIFN_795X
	tristate "Driver HIFN 795x crypto accelerator chips"
224
	select CRYPTO_DES
225
	select CRYPTO_BLKCIPHER
226
	select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG
227
	depends on PCI
228
	depends on !ARCH_DMA_ADDR_T_64BIT
229 230 231
	help
	  This option allows you to have support for HIFN 795x crypto adapters.

232 233 234 235 236 237
config CRYPTO_DEV_HIFN_795X_RNG
	bool "HIFN 795x random number generator"
	depends on CRYPTO_DEV_HIFN_795X
	help
	  Select this option if you want to enable the random number generator
	  on the HIFN 795x crypto adapters.
238

239 240
source drivers/crypto/caam/Kconfig

241 242
config CRYPTO_DEV_TALITOS
	tristate "Talitos Freescale Security Engine (SEC)"
243
	select CRYPTO_AEAD
244
	select CRYPTO_AUTHENC
245 246
	select CRYPTO_BLKCIPHER
	select CRYPTO_HASH
247 248 249 250 251 252 253 254 255 256 257 258
	select HW_RANDOM
	depends on FSL_SOC
	help
	  Say 'Y' here to use the Freescale Security Engine (SEC)
	  to offload cryptographic algorithm computation.

	  The Freescale SEC is present on PowerQUICC 'E' processors, such
	  as the MPC8349E and MPC8548E.

	  To compile this driver as a module, choose M here: the module
	  will be called talitos.

259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276
config CRYPTO_DEV_TALITOS1
	bool "SEC1 (SEC 1.0 and SEC Lite 1.2)"
	depends on CRYPTO_DEV_TALITOS
	depends on PPC_8xx || PPC_82xx
	default y
	help
	  Say 'Y' here to use the Freescale Security Engine (SEC) version 1.0
	  found on MPC82xx or the Freescale Security Engine (SEC Lite)
	  version 1.2 found on MPC8xx

config CRYPTO_DEV_TALITOS2
	bool "SEC2+ (SEC version 2.0 or upper)"
	depends on CRYPTO_DEV_TALITOS
	default y if !PPC_8xx
	help
	  Say 'Y' here to use the Freescale Security Engine (SEC)
	  version 2 and following as found on MPC83xx, MPC85xx, etc ...

277 278
config CRYPTO_DEV_IXP4XX
	tristate "Driver for IXP4xx crypto hardware acceleration"
279
	depends on ARCH_IXP4XX && IXP4XX_QMGR && IXP4XX_NPE
280
	select CRYPTO_DES
281
	select CRYPTO_AEAD
282
	select CRYPTO_AUTHENC
283 284 285 286
	select CRYPTO_BLKCIPHER
	help
	  Driver for the IXP4xx NPE crypto engine.

J
James Hsiao 已提交
287 288 289 290 291 292 293 294
config CRYPTO_DEV_PPC4XX
	tristate "Driver AMCC PPC4xx crypto accelerator"
	depends on PPC && 4xx
	select CRYPTO_HASH
	select CRYPTO_BLKCIPHER
	help
	  This option allows you to have support for AMCC crypto acceleration.

295 296 297 298 299 300 301 302
config HW_RANDOM_PPC4XX
	bool "PowerPC 4xx generic true random number generator support"
	depends on CRYPTO_DEV_PPC4XX && HW_RANDOM
	default y
	---help---
	 This option provides the kernel-side support for the TRNG hardware
	 found in the security function of some PowerPC 4xx SoCs.

303
config CRYPTO_DEV_OMAP_SHAM
304 305
	tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator"
	depends on ARCH_OMAP2PLUS
306 307
	select CRYPTO_SHA1
	select CRYPTO_MD5
308 309 310
	select CRYPTO_SHA256
	select CRYPTO_SHA512
	select CRYPTO_HMAC
311
	help
312 313
	  OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you
	  want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
314

315 316
config CRYPTO_DEV_OMAP_AES
	tristate "Support for OMAP AES hw engine"
317
	depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS
318
	select CRYPTO_AES
319
	select CRYPTO_BLKCIPHER
320
	select CRYPTO_ENGINE
321 322 323
	select CRYPTO_CBC
	select CRYPTO_ECB
	select CRYPTO_CTR
324 325 326 327
	help
	  OMAP processors have AES module accelerator. Select this if you
	  want to use the OMAP module for AES algorithms.

328
config CRYPTO_DEV_OMAP_DES
329
	tristate "Support for OMAP DES/3DES hw engine"
330 331
	depends on ARCH_OMAP2PLUS
	select CRYPTO_DES
332
	select CRYPTO_BLKCIPHER
333
	select CRYPTO_ENGINE
334 335 336
	help
	  OMAP processors have DES/3DES module accelerator. Select this if you
	  want to use the OMAP module for DES and 3DES algorithms. Currently
337 338
	  the ECB and CBC modes of operation are supported by the driver. Also
	  accesses made on unaligned boundaries are supported.
339

340 341
config CRYPTO_DEV_PICOXCELL
	tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
342
	depends on ARCH_PICOXCELL && HAVE_CLK
343
	select CRYPTO_AEAD
344 345
	select CRYPTO_AES
	select CRYPTO_AUTHENC
346
	select CRYPTO_BLKCIPHER
347 348 349 350 351 352 353 354 355 356 357
	select CRYPTO_DES
	select CRYPTO_CBC
	select CRYPTO_ECB
	select CRYPTO_SEQIV
	help
	  This option enables support for the hardware offload engines in the
	  Picochip picoXcell SoC devices. Select this for IPSEC ESP offload
	  and for 3gpp Layer 2 ciphering support.

	  Saying m here will build a module named pipcoxcell_crypto.

358 359
config CRYPTO_DEV_SAHARA
	tristate "Support for SAHARA crypto accelerator"
360
	depends on ARCH_MXC && OF
361 362 363 364 365 366 367
	select CRYPTO_BLKCIPHER
	select CRYPTO_AES
	select CRYPTO_ECB
	help
	  This option enables support for the SAHARA HW crypto accelerator
	  found in some Freescale i.MX chips.

368 369 370 371 372 373 374 375 376
config CRYPTO_DEV_MXC_SCC
	tristate "Support for Freescale Security Controller (SCC)"
	depends on ARCH_MXC && OF
	select CRYPTO_BLKCIPHER
	select CRYPTO_DES
	help
	  This option enables support for the Security Controller (SCC)
	  found in Freescale i.MX25 chips.

377
config CRYPTO_DEV_S5P
378
	tristate "Support for Samsung S5PV210/Exynos crypto accelerator"
379 380
	depends on ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST
	depends on HAS_IOMEM && HAS_DMA
381 382 383 384
	select CRYPTO_AES
	select CRYPTO_BLKCIPHER
	help
	  This option allows you to have support for S5P crypto acceleration.
385
	  Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES
386 387
	  algorithms execution.

388
config CRYPTO_DEV_NX
389 390
	bool "Support for IBM PowerPC Nest (NX) cryptographic acceleration"
	depends on PPC64
391
	help
392 393 394 395
	  This enables support for the NX hardware cryptographic accelerator
	  coprocessor that is in IBM PowerPC P7+ or later processors.  This
	  does not actually enable any drivers, it only allows you to select
	  which acceleration type (encryption and/or compression) to enable.
S
Seth Jennings 已提交
396 397 398 399

if CRYPTO_DEV_NX
	source "drivers/crypto/nx/Kconfig"
endif
400

401 402 403 404 405 406 407 408 409 410
config CRYPTO_DEV_UX500
	tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration"
	depends on ARCH_U8500
	help
	  Driver for ST-Ericsson UX500 crypto engine.

if CRYPTO_DEV_UX500
	source "drivers/crypto/ux500/Kconfig"
endif # if CRYPTO_DEV_UX500

411 412 413 414 415 416 417
config CRYPTO_DEV_BFIN_CRC
	tristate "Support for Blackfin CRC hardware"
	depends on BF60x
	help
	  Newer Blackfin processors have CRC hardware. Select this if you
	  want to use the Blackfin CRC module.

418 419
config CRYPTO_DEV_ATMEL_AES
	tristate "Support for Atmel AES hw accelerator"
420
	depends on HAS_DMA
A
Arnd Bergmann 已提交
421
	depends on AT_XDMAC || AT_HDMAC || COMPILE_TEST
422
	select CRYPTO_AES
423
	select CRYPTO_AEAD
424 425 426 427 428 429 430 431 432
	select CRYPTO_BLKCIPHER
	help
	  Some Atmel processors have AES hw accelerator.
	  Select this if you want to use the Atmel module for
	  AES algorithms.

	  To compile this driver as a module, choose M here: the module
	  will be called atmel-aes.

433 434 435 436 437 438 439 440 441 442 443 444 445
config CRYPTO_DEV_ATMEL_TDES
	tristate "Support for Atmel DES/TDES hw accelerator"
	depends on ARCH_AT91
	select CRYPTO_DES
	select CRYPTO_BLKCIPHER
	help
	  Some Atmel processors have DES/TDES hw accelerator.
	  Select this if you want to use the Atmel module for
	  DES/TDES algorithms.

	  To compile this driver as a module, choose M here: the module
	  will be called atmel-tdes.

446
config CRYPTO_DEV_ATMEL_SHA
447
	tristate "Support for Atmel SHA hw accelerator"
448
	depends on ARCH_AT91
449
	select CRYPTO_HASH
450
	help
451 452
	  Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
	  hw accelerator.
453
	  Select this if you want to use the Atmel module for
454
	  SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
455 456 457 458

	  To compile this driver as a module, choose M here: the module
	  will be called atmel-sha.

459 460
config CRYPTO_DEV_CCP
	bool "Support for AMD Cryptographic Coprocessor"
T
Tom Lendacky 已提交
461
	depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM
462
	help
463
	  The AMD Cryptographic Coprocessor provides hardware offload support
464 465 466 467 468 469
	  for encryption, hashing and related operations.

if CRYPTO_DEV_CCP
	source "drivers/crypto/ccp/Kconfig"
endif

470 471
config CRYPTO_DEV_MXS_DCP
	tristate "Support for Freescale MXS DCP"
472
	depends on (ARCH_MXS || ARCH_MXC)
473
	select STMP_DEVICE
474 475 476 477
	select CRYPTO_CBC
	select CRYPTO_ECB
	select CRYPTO_AES
	select CRYPTO_BLKCIPHER
478
	select CRYPTO_HASH
479 480 481 482 483 484 485
	help
	  The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB
	  co-processor on the die.

	  To compile this driver as a module, choose M here: the module
	  will be called mxs-dcp.

486
source "drivers/crypto/qat/Kconfig"
487 488 489

config CRYPTO_DEV_QCE
	tristate "Qualcomm crypto engine accelerator"
490
	depends on (ARCH_QCOM || COMPILE_TEST) && HAS_DMA && HAS_IOMEM
491 492 493 494 495 496 497 498 499 500 501 502
	select CRYPTO_AES
	select CRYPTO_DES
	select CRYPTO_ECB
	select CRYPTO_CBC
	select CRYPTO_XTS
	select CRYPTO_CTR
	select CRYPTO_BLKCIPHER
	help
	  This driver supports Qualcomm crypto engine accelerator
	  hardware. To compile this driver as a module, choose M here. The
	  module will be called qcrypto.

503 504
config CRYPTO_DEV_VMX
	bool "Support for VMX cryptographic acceleration instructions"
505
	depends on PPC64 && VSX
506 507 508 509 510
	help
	  Support for VMX cryptographic acceleration instructions.

source "drivers/crypto/vmx/Kconfig"

511 512
config CRYPTO_DEV_IMGTEC_HASH
	tristate "Imagination Technologies hardware hash accelerator"
513 514
	depends on MIPS || COMPILE_TEST
	depends on HAS_DMA
515 516 517 518 519 520 521 522 523
	select CRYPTO_MD5
	select CRYPTO_SHA1
	select CRYPTO_SHA256
	select CRYPTO_HASH
	help
	  This driver interfaces with the Imagination Technologies
	  hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256
	  hashing algorithms.

524 525
config CRYPTO_DEV_SUN4I_SS
	tristate "Support for Allwinner Security System cryptographic accelerator"
526
	depends on ARCH_SUNXI && !64BIT
527 528 529 530 531 532 533 534 535 536 537 538 539 540
	select CRYPTO_MD5
	select CRYPTO_SHA1
	select CRYPTO_AES
	select CRYPTO_DES
	select CRYPTO_BLKCIPHER
	help
	  Some Allwinner SoC have a crypto accelerator named
	  Security System. Select this if you want to use it.
	  The Security System handle AES/DES/3DES ciphers in CBC mode
	  and SHA1 and MD5 hash algorithms.

	  To compile this driver as a module, choose M here: the module
	  will be called sun4i-ss.

541 542 543 544 545
config CRYPTO_DEV_ROCKCHIP
	tristate "Rockchip's Cryptographic Engine driver"
	depends on OF && ARCH_ROCKCHIP
	select CRYPTO_AES
	select CRYPTO_DES
546 547 548 549
	select CRYPTO_MD5
	select CRYPTO_SHA1
	select CRYPTO_SHA256
	select CRYPTO_HASH
550 551 552 553 554 555
	select CRYPTO_BLKCIPHER

	help
	  This driver interfaces with the hardware crypto accelerator.
	  Supporting cbc/ecb chainmode, and aes/des/des3_ede cipher mode.

556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572
config CRYPTO_DEV_MEDIATEK
	tristate "MediaTek's EIP97 Cryptographic Engine driver"
	depends on ARM && (ARCH_MEDIATEK || COMPILE_TEST)
	select NEON
	select KERNEL_MODE_NEON
	select ARM_CRYPTO
	select CRYPTO_AES
	select CRYPTO_BLKCIPHER
	select CRYPTO_SHA1_ARM_NEON
	select CRYPTO_SHA256_ARM
	select CRYPTO_SHA512_ARM
	select CRYPTO_HMAC
	help
	  This driver allows you to utilize the hardware crypto accelerator
	  EIP97 which can be found on the MT7623 MT2701, MT8521p, etc ....
	  Select this if you want to use it for AES/SHA1/SHA2 algorithms.

573 574
source "drivers/crypto/chelsio/Kconfig"

G
Gonglei 已提交
575 576
source "drivers/crypto/virtio/Kconfig"

577
endif # CRYPTO_HW