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 && IXP4XX_QMGR && IXP4XX_NPE
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 MD5/SHA1/SHA2 hw accelerator"
246	depends on ARCH_OMAP2PLUS
247	select CRYPTO_SHA1
248	select CRYPTO_MD5
249	select CRYPTO_SHA256
250	select CRYPTO_SHA512
251	select CRYPTO_HMAC
252	help
253	  OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you
254	  want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
255
256config CRYPTO_DEV_OMAP_AES
257	tristate "Support for OMAP AES hw engine"
258	depends on ARCH_OMAP2 || ARCH_OMAP3 || ARCH_OMAP2PLUS
259	select CRYPTO_AES
260	select CRYPTO_BLKCIPHER2
261	help
262	  OMAP processors have AES module accelerator. Select this if you
263	  want to use the OMAP module for AES algorithms.
264
265config CRYPTO_DEV_OMAP_DES
266	tristate "Support for OMAP DES3DES hw engine"
267	depends on ARCH_OMAP2PLUS
268	select CRYPTO_DES
269	select CRYPTO_BLKCIPHER2
270	help
271	  OMAP processors have DES/3DES module accelerator. Select this if you
272	  want to use the OMAP module for DES and 3DES algorithms. Currently
273	  the ECB and CBC modes of operation supported by the driver. Also
274	  accesses made on unaligned boundaries are also supported.
275
276config CRYPTO_DEV_PICOXCELL
277	tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
278	depends on ARCH_PICOXCELL && HAVE_CLK
279	select CRYPTO_AES
280	select CRYPTO_AUTHENC
281	select CRYPTO_ALGAPI
282	select CRYPTO_DES
283	select CRYPTO_CBC
284	select CRYPTO_ECB
285	select CRYPTO_SEQIV
286	help
287	  This option enables support for the hardware offload engines in the
288	  Picochip picoXcell SoC devices. Select this for IPSEC ESP offload
289	  and for 3gpp Layer 2 ciphering support.
290
291	  Saying m here will build a module named pipcoxcell_crypto.
292
293config CRYPTO_DEV_SAHARA
294	tristate "Support for SAHARA crypto accelerator"
295	depends on ARCH_MXC && OF
296	select CRYPTO_BLKCIPHER
297	select CRYPTO_AES
298	select CRYPTO_ECB
299	help
300	  This option enables support for the SAHARA HW crypto accelerator
301	  found in some Freescale i.MX chips.
302
303config CRYPTO_DEV_S5P
304	tristate "Support for Samsung S5PV210/Exynos crypto accelerator"
305	depends on ARCH_S5PV210 || ARCH_EXYNOS
306	select CRYPTO_AES
307	select CRYPTO_ALGAPI
308	select CRYPTO_BLKCIPHER
309	help
310	  This option allows you to have support for S5P crypto acceleration.
311	  Select this to offload Samsung S5PV210 or S5PC110, Exynos from AES
312	  algorithms execution.
313
314config CRYPTO_DEV_NX
315	bool "Support for IBM Power7+ in-Nest cryptographic acceleration"
316	depends on PPC64 && IBMVIO && !CPU_LITTLE_ENDIAN
317	default n
318	help
319	  Support for Power7+ in-Nest cryptographic acceleration.
320
321if CRYPTO_DEV_NX
322	source "drivers/crypto/nx/Kconfig"
323endif
324
325config CRYPTO_DEV_UX500
326	tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration"
327	depends on ARCH_U8500
328	select CRYPTO_ALGAPI
329	help
330	  Driver for ST-Ericsson UX500 crypto engine.
331
332if CRYPTO_DEV_UX500
333	source "drivers/crypto/ux500/Kconfig"
334endif # if CRYPTO_DEV_UX500
335
336config CRYPTO_DEV_BFIN_CRC
337	tristate "Support for Blackfin CRC hardware"
338	depends on BF60x
339	help
340	  Newer Blackfin processors have CRC hardware. Select this if you
341	  want to use the Blackfin CRC module.
342
343config CRYPTO_DEV_ATMEL_AES
344	tristate "Support for Atmel AES hw accelerator"
345	depends on ARCH_AT91
346	select CRYPTO_CBC
347	select CRYPTO_ECB
348	select CRYPTO_AES
349	select CRYPTO_ALGAPI
350	select CRYPTO_BLKCIPHER
351	select AT_HDMAC
352	help
353	  Some Atmel processors have AES hw accelerator.
354	  Select this if you want to use the Atmel module for
355	  AES algorithms.
356
357	  To compile this driver as a module, choose M here: the module
358	  will be called atmel-aes.
359
360config CRYPTO_DEV_ATMEL_TDES
361	tristate "Support for Atmel DES/TDES hw accelerator"
362	depends on ARCH_AT91
363	select CRYPTO_DES
364	select CRYPTO_CBC
365	select CRYPTO_ECB
366	select CRYPTO_ALGAPI
367	select CRYPTO_BLKCIPHER
368	help
369	  Some Atmel processors have DES/TDES hw accelerator.
370	  Select this if you want to use the Atmel module for
371	  DES/TDES algorithms.
372
373	  To compile this driver as a module, choose M here: the module
374	  will be called atmel-tdes.
375
376config CRYPTO_DEV_ATMEL_SHA
377	tristate "Support for Atmel SHA hw accelerator"
378	depends on ARCH_AT91
379	select CRYPTO_SHA1
380	select CRYPTO_SHA256
381	select CRYPTO_SHA512
382	select CRYPTO_ALGAPI
383	help
384	  Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
385	  hw accelerator.
386	  Select this if you want to use the Atmel module for
387	  SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
388
389	  To compile this driver as a module, choose M here: the module
390	  will be called atmel-sha.
391
392config CRYPTO_DEV_CCP
393	bool "Support for AMD Cryptographic Coprocessor"
394	depends on ((X86 && PCI) || (ARM64 && (OF_ADDRESS || ACPI))) && HAS_IOMEM
395	default n
396	help
397	  The AMD Cryptographic Coprocessor provides hardware support
398	  for encryption, hashing and related operations.
399
400if CRYPTO_DEV_CCP
401	source "drivers/crypto/ccp/Kconfig"
402endif
403
404config CRYPTO_DEV_MXS_DCP
405	tristate "Support for Freescale MXS DCP"
406	depends on ARCH_MXS
407	select CRYPTO_SHA1
408	select CRYPTO_SHA256
409	select CRYPTO_CBC
410	select CRYPTO_ECB
411	select CRYPTO_AES
412	select CRYPTO_BLKCIPHER
413	select CRYPTO_ALGAPI
414	help
415	  The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB
416	  co-processor on the die.
417
418	  To compile this driver as a module, choose M here: the module
419	  will be called mxs-dcp.
420
421source "drivers/crypto/qat/Kconfig"
422
423config CRYPTO_DEV_QCE
424	tristate "Qualcomm crypto engine accelerator"
425	depends on (ARCH_QCOM || COMPILE_TEST) && HAS_DMA && HAS_IOMEM
426	select CRYPTO_AES
427	select CRYPTO_DES
428	select CRYPTO_ECB
429	select CRYPTO_CBC
430	select CRYPTO_XTS
431	select CRYPTO_CTR
432	select CRYPTO_ALGAPI
433	select CRYPTO_BLKCIPHER
434	help
435	  This driver supports Qualcomm crypto engine accelerator
436	  hardware. To compile this driver as a module, choose M here. The
437	  module will be called qcrypto.
438
439config CRYPTO_DEV_VMX
440	bool "Support for VMX cryptographic acceleration instructions"
441	depends on PPC64
442	default n
443	help
444	  Support for VMX cryptographic acceleration instructions.
445
446source "drivers/crypto/vmx/Kconfig"
447
448config CRYPTO_DEV_IMGTEC_HASH
449	tristate "Imagination Technologies hardware hash accelerator"
450	depends on MIPS || COMPILE_TEST
451	depends on HAS_DMA
452	select CRYPTO_ALGAPI
453	select CRYPTO_MD5
454	select CRYPTO_SHA1
455	select CRYPTO_SHA256
456	select CRYPTO_HASH
457	help
458	  This driver interfaces with the Imagination Technologies
459	  hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256
460	  hashing algorithms.
461
462endif # CRYPTO_HW
463