diff options
| author | Antoine Ténart | 2017-05-24 16:10:34 +0200 |
|---|---|---|
| committer | Herbert Xu | 2017-06-10 06:04:21 +0200 |
| commit | 1b44c5a60c137e5fd0c2c8b86e58fdbc9cd181ce (patch) | |
| tree | 963e4bea0aadf317d3d32114da91373577f7073c /drivers/crypto/Kconfig | |
| parent | crypto: omap-sham - force word alignment on the xmit-buf also (diff) | |
| download | kernel-qcow2-linux-1b44c5a60c137e5fd0c2c8b86e58fdbc9cd181ce.tar.gz kernel-qcow2-linux-1b44c5a60c137e5fd0c2c8b86e58fdbc9cd181ce.tar.xz kernel-qcow2-linux-1b44c5a60c137e5fd0c2c8b86e58fdbc9cd181ce.zip | |
crypto: inside-secure - add SafeXcel EIP197 crypto engine driver
Add support for Inside Secure SafeXcel EIP197 cryptographic engine,
which can be found on Marvell Armada 7k and 8k boards. This driver
currently implements: ecb(aes), cbc(aes), sha1, sha224, sha256 and
hmac(sah1) algorithms.
Two firmwares are needed for this engine to work. Their are mostly used
for more advanced operations than the ones supported (as of now), but we
still need them to pass the data to the internal cryptographic engine.
Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/Kconfig')
| -rw-r--r-- | drivers/crypto/Kconfig | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig index 4e6591b0b128..0a652baf3cb3 100644 --- a/drivers/crypto/Kconfig +++ b/drivers/crypto/Kconfig @@ -655,4 +655,21 @@ config CRYPTO_DEV_BCM_SPU source "drivers/crypto/stm32/Kconfig" +config CRYPTO_DEV_SAFEXCEL + tristate "Inside Secure's SafeXcel cryptographic engine driver" + depends on HAS_DMA && OF + depends on (ARM64 && ARCH_MVEBU) || (COMPILE_TEST && 64BIT) + select CRYPTO_AES + select CRYPTO_BLKCIPHER + select CRYPTO_HASH + select CRYPTO_HMAC + select CRYPTO_SHA1 + select CRYPTO_SHA256 + select CRYPTO_SHA512 + help + This driver interfaces with the SafeXcel EIP-197 cryptographic engine + designed by Inside Secure. Select this if you want to use CBC/ECB + chain mode, AES cipher mode and SHA1/SHA224/SHA256/SHA512 hash + algorithms. + endif # CRYPTO_HW |