From: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
To: Sebastian Andrzej Siewior <arm-kernel@ml.breakpoint.cc>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-crypto@vger.kernel.org
Subject: Re: [WIP/RFC] crypto: add support for Orion5X crypto engine
Date: Wed, 18 Mar 2009 17:55:17 +0200 [thread overview]
Message-ID: <49C11965.9000200@teltonika.lt> (raw)
In-Reply-To: <20090317215844.GA23739@Chamillionaire.breakpoint.cc>
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@breakpoint.cc>
> ---
> 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.
> +
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2009-03-18 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 21:58 [WIP/RFC] crypto: add support for Orion5X crypto engine Sebastian Andrzej Siewior
2009-03-17 22:42 ` Evgeniy Polyakov
2009-03-18 21:57 ` Sebastian Andrzej Siewior
2009-03-18 15:55 ` Paulius Zaleckas [this message]
2009-03-18 16:33 ` Martin Michlmayr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C11965.9000200@teltonika.lt \
--to=paulius.zaleckas@teltonika.lt \
--cc=arm-kernel@ml.breakpoint.cc \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox