[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150517124811.797fab32@bbrezillon>
Date: Sun, 17 May 2015 12:48:11 +0200
From: Boris Brezillon <boris.brezillon@...e-electrons.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: LABBE Corentin <clabbe.montjoie@...il.com>, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
maxime.ripard@...e-electrons.com, linux@....linux.org.uk,
davem@...emloft.net, akpm@...ux-foundation.org,
gregkh@...uxfoundation.org, mchehab@....samsung.com,
joe@...ches.com, tj@...nel.org, arnd@...db.de,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-sunxi@...glegroups.com
Subject: Re: [PATCH v9 4/4] crypto: Add Allwinner Security System crypto
accelerator
Hi Herbert,
On Sun, 17 May 2015 18:34:40 +0800
Herbert Xu <herbert@...dor.apana.org.au> wrote:
> On Sun, May 17, 2015 at 10:45:08AM +0200, Boris Brezillon wrote:
> >
> > From my POV this is not asynchronous at all (see my comments inline),
> > but maybe Herbert can confirm that.
>
> Well we don't actually require drivers to be asynchronous. It is
> obviously the preferred method but some hardware may not be capable
> of that.
Yep, but then they shouldn't be declared with CRYPTO_ALG_ASYNC and as an
ablkcipher algorithm (*Asynchronous* Block Cipher), right ?
Regarding the capabilities of this crypto engine, from what I've seen,
it is definitely capable of doing asynchronous requests ;-).
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists