Kconfig 8.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279
  1. menuconfig CRYPTO_HW
  2. bool "Hardware crypto devices"
  3. default y
  4. ---help---
  5. Say Y here to get to see options for hardware crypto devices and
  6. processors. This option alone does not add any kernel code.
  7. If you say N, all options in this submenu will be skipped and disabled.
  8. if CRYPTO_HW
  9. config CRYPTO_DEV_PADLOCK
  10. tristate "Support for VIA PadLock ACE"
  11. depends on X86 && !UML
  12. help
  13. Some VIA processors come with an integrated crypto engine
  14. (so called VIA PadLock ACE, Advanced Cryptography Engine)
  15. that provides instructions for very fast cryptographic
  16. operations with supported algorithms.
  17. The instructions are used only when the CPU supports them.
  18. Otherwise software encryption is used.
  19. config CRYPTO_DEV_PADLOCK_AES
  20. tristate "PadLock driver for AES algorithm"
  21. depends on CRYPTO_DEV_PADLOCK
  22. select CRYPTO_BLKCIPHER
  23. select CRYPTO_AES
  24. help
  25. Use VIA PadLock for AES algorithm.
  26. Available in VIA C3 and newer CPUs.
  27. If unsure say M. The compiled module will be
  28. called padlock-aes.
  29. config CRYPTO_DEV_PADLOCK_SHA
  30. tristate "PadLock driver for SHA1 and SHA256 algorithms"
  31. depends on CRYPTO_DEV_PADLOCK
  32. select CRYPTO_HASH
  33. select CRYPTO_SHA1
  34. select CRYPTO_SHA256
  35. help
  36. Use VIA PadLock for SHA1/SHA256 algorithms.
  37. Available in VIA C7 and newer processors.
  38. If unsure say M. The compiled module will be
  39. called padlock-sha.
  40. config CRYPTO_DEV_GEODE
  41. tristate "Support for the Geode LX AES engine"
  42. depends on X86_32 && PCI
  43. select CRYPTO_ALGAPI
  44. select CRYPTO_BLKCIPHER
  45. help
  46. Say 'Y' here to use the AMD Geode LX processor on-board AES
  47. engine for the CryptoAPI AES algorithm.
  48. To compile this driver as a module, choose M here: the module
  49. will be called geode-aes.
  50. config ZCRYPT
  51. tristate "Support for PCI-attached cryptographic adapters"
  52. depends on S390
  53. select ZCRYPT_MONOLITHIC if ZCRYPT="y"
  54. select HW_RANDOM
  55. help
  56. Select this option if you want to use a PCI-attached cryptographic
  57. adapter like:
  58. + PCI Cryptographic Accelerator (PCICA)
  59. + PCI Cryptographic Coprocessor (PCICC)
  60. + PCI-X Cryptographic Coprocessor (PCIXCC)
  61. + Crypto Express2 Coprocessor (CEX2C)
  62. + Crypto Express2 Accelerator (CEX2A)
  63. config ZCRYPT_MONOLITHIC
  64. bool "Monolithic zcrypt module"
  65. depends on ZCRYPT
  66. help
  67. Select this option if you want to have a single module z90crypt,
  68. that contains all parts of the crypto device driver (ap bus,
  69. request router and all the card drivers).
  70. config CRYPTO_SHA1_S390
  71. tristate "SHA1 digest algorithm"
  72. depends on S390
  73. select CRYPTO_HASH
  74. help
  75. This is the s390 hardware accelerated implementation of the
  76. SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
  77. config CRYPTO_SHA256_S390
  78. tristate "SHA256 digest algorithm"
  79. depends on S390
  80. select CRYPTO_HASH
  81. help
  82. This is the s390 hardware accelerated implementation of the
  83. SHA256 secure hash standard (DFIPS 180-2).
  84. This version of SHA implements a 256 bit hash with 128 bits of
  85. security against collision attacks.
  86. config CRYPTO_SHA512_S390
  87. tristate "SHA384 and SHA512 digest algorithm"
  88. depends on S390
  89. select CRYPTO_HASH
  90. help
  91. This is the s390 hardware accelerated implementation of the
  92. SHA512 secure hash standard.
  93. This version of SHA implements a 512 bit hash with 256 bits of
  94. security against collision attacks. The code also includes SHA-384,
  95. a 384 bit hash with 192 bits of security against collision attacks.
  96. config CRYPTO_DES_S390
  97. tristate "DES and Triple DES cipher algorithms"
  98. depends on S390
  99. select CRYPTO_ALGAPI
  100. select CRYPTO_BLKCIPHER
  101. help
  102. This us the s390 hardware accelerated implementation of the
  103. DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
  104. config CRYPTO_AES_S390
  105. tristate "AES cipher algorithms"
  106. depends on S390
  107. select CRYPTO_ALGAPI
  108. select CRYPTO_BLKCIPHER
  109. help
  110. This is the s390 hardware accelerated implementation of the
  111. AES cipher algorithms (FIPS-197).
  112. As of z9 the ECB and CBC modes are hardware accelerated
  113. for 128 bit keys.
  114. As of z10 the ECB and CBC modes are hardware accelerated
  115. for all AES key sizes.
  116. As of z196 the XTS mode is hardware accelerated for 256 and
  117. 512 bit keys.
  118. config S390_PRNG
  119. tristate "Pseudo random number generator device driver"
  120. depends on S390
  121. default "m"
  122. help
  123. Select this option if you want to use the s390 pseudo random number
  124. generator. The PRNG is part of the cryptographic processor functions
  125. and uses triple-DES to generate secure random numbers like the
  126. ANSI X9.17 standard. The PRNG is usable via the char device
  127. /dev/prandom.
  128. config CRYPTO_DEV_MV_CESA
  129. tristate "Marvell's Cryptographic Engine"
  130. depends on PLAT_ORION
  131. select CRYPTO_ALGAPI
  132. select CRYPTO_AES
  133. select CRYPTO_BLKCIPHER2
  134. help
  135. This driver allows you to utilize the Cryptographic Engines and
  136. Security Accelerator (CESA) which can be found on the Marvell Orion
  137. and Kirkwood SoCs, such as QNAP's TS-209.
  138. Currently the driver supports AES in ECB and CBC mode without DMA.
  139. config CRYPTO_DEV_NIAGARA2
  140. tristate "Niagara2 Stream Processing Unit driver"
  141. select CRYPTO_DES
  142. select CRYPTO_ALGAPI
  143. depends on SPARC64
  144. help
  145. Each core of a Niagara2 processor contains a Stream
  146. Processing Unit, which itself contains several cryptographic
  147. sub-units. One set provides the Modular Arithmetic Unit,
  148. used for SSL offload. The other set provides the Cipher
  149. Group, which can perform encryption, decryption, hashing,
  150. checksumming, and raw copies.
  151. config CRYPTO_DEV_HIFN_795X
  152. tristate "Driver HIFN 795x crypto accelerator chips"
  153. select CRYPTO_DES
  154. select CRYPTO_ALGAPI
  155. select CRYPTO_BLKCIPHER
  156. select HW_RANDOM if CRYPTO_DEV_HIFN_795X_RNG
  157. depends on PCI
  158. help
  159. This option allows you to have support for HIFN 795x crypto adapters.
  160. config CRYPTO_DEV_HIFN_795X_RNG
  161. bool "HIFN 795x random number generator"
  162. depends on CRYPTO_DEV_HIFN_795X
  163. help
  164. Select this option if you want to enable the random number generator
  165. on the HIFN 795x crypto adapters.
  166. source drivers/crypto/caam/Kconfig
  167. config CRYPTO_DEV_TALITOS
  168. tristate "Talitos Freescale Security Engine (SEC)"
  169. select CRYPTO_ALGAPI
  170. select CRYPTO_AUTHENC
  171. select HW_RANDOM
  172. depends on FSL_SOC
  173. help
  174. Say 'Y' here to use the Freescale Security Engine (SEC)
  175. to offload cryptographic algorithm computation.
  176. The Freescale SEC is present on PowerQUICC 'E' processors, such
  177. as the MPC8349E and MPC8548E.
  178. To compile this driver as a module, choose M here: the module
  179. will be called talitos.
  180. config CRYPTO_DEV_IXP4XX
  181. tristate "Driver for IXP4xx crypto hardware acceleration"
  182. depends on ARCH_IXP4XX
  183. select CRYPTO_DES
  184. select CRYPTO_ALGAPI
  185. select CRYPTO_AUTHENC
  186. select CRYPTO_BLKCIPHER
  187. help
  188. Driver for the IXP4xx NPE crypto engine.
  189. config CRYPTO_DEV_PPC4XX
  190. tristate "Driver AMCC PPC4xx crypto accelerator"
  191. depends on PPC && 4xx
  192. select CRYPTO_HASH
  193. select CRYPTO_ALGAPI
  194. select CRYPTO_BLKCIPHER
  195. help
  196. This option allows you to have support for AMCC crypto acceleration.
  197. config CRYPTO_DEV_OMAP_SHAM
  198. tristate "Support for OMAP SHA1/MD5 hw accelerator"
  199. depends on ARCH_OMAP2 || ARCH_OMAP3
  200. select CRYPTO_SHA1
  201. select CRYPTO_MD5
  202. help
  203. OMAP processors have SHA1/MD5 hw accelerator. Select this if you
  204. want to use the OMAP module for SHA1/MD5 algorithms.
  205. config CRYPTO_DEV_OMAP_AES
  206. tristate "Support for OMAP AES hw engine"
  207. depends on ARCH_OMAP2 || ARCH_OMAP3
  208. select CRYPTO_AES
  209. help
  210. OMAP processors have AES module accelerator. Select this if you
  211. want to use the OMAP module for AES algorithms.
  212. config CRYPTO_DEV_PICOXCELL
  213. tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
  214. depends on ARCH_PICOXCELL
  215. select CRYPTO_AES
  216. select CRYPTO_AUTHENC
  217. select CRYPTO_ALGAPI
  218. select CRYPTO_DES
  219. select CRYPTO_CBC
  220. select CRYPTO_ECB
  221. select CRYPTO_SEQIV
  222. help
  223. This option enables support for the hardware offload engines in the
  224. Picochip picoXcell SoC devices. Select this for IPSEC ESP offload
  225. and for 3gpp Layer 2 ciphering support.
  226. Saying m here will build a module named pipcoxcell_crypto.
  227. config CRYPTO_DEV_S5P
  228. tristate "Support for Samsung S5PV210 crypto accelerator"
  229. depends on ARCH_S5PV210
  230. select CRYPTO_AES
  231. select CRYPTO_ALGAPI
  232. select CRYPTO_BLKCIPHER
  233. help
  234. This option allows you to have support for S5P crypto acceleration.
  235. Select this to offload Samsung S5PV210 or S5PC110 from AES
  236. algorithms execution.
  237. endif # CRYPTO_HW