Sebastian Andrzej Siewior wrote: > This is version two of the the driver. New things: > - aes-ecb passes selftests > - aes-cbc passes selftests > > The driver still does memcpy() from/to sram. To solve this, a dma driver > would be required but first I wanted to compare the performance between > now and nothing/generic aes. However I managed to crash cryptsetup with > luksOpen. Got look into this... > > Signed-off-by: Sebastian Andrzej Siewior <sebastian@xxxxxxxxxxxxx> > --- > drivers/crypto/Kconfig | 9 + > drivers/crypto/Makefile | 1 + > drivers/crypto/mav_crypto.c | 724 +++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 734 insertions(+), 0 deletions(-) > create mode 100644 drivers/crypto/mav_crypto.c > > diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig > index 01afd75..514fe78 100644 > --- a/drivers/crypto/Kconfig > +++ b/drivers/crypto/Kconfig > @@ -157,6 +157,15 @@ config S390_PRNG > ANSI X9.17 standard. The PRNG is usable via the char device > /dev/prandom. > > +config CRYPTO_DEV_MARVELL_CRYPTO_ENGINE CRYPTO_DEV...CRYPTO_ENGINE Maybe CRYPTO_DEV_MARVELL would be enough? > + tristate "Marvell's Cryptographic Engine" > + depends on PLAT_ORION > + select CRYPTO_ALGAPI > + select CRYPTO_AES > + help > + This driver allows you utilize the cryptographic engine which can be > + found on certain SoC like QNAP's TS-209. > + -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
