mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Anand Moon <linux.amoon@gmail.com>,
	Kevin Hilman <khilman@baylibre.com>,
	linux-kernel@vger.kernel.org,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Corentin Labbe <clabbe@baylibre.com>,
	linux-amlogic@lists.infradead.org,
	"David S . Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCHv1 0/3] Enable crypto module on Amlogic GXBB SoC platform
Date: Wed, 11 Dec 2019 10:32:01 +0100	[thread overview]
Message-ID: <d2b54743-87da-091e-8d62-288ee29a54b0@baylibre.com> (raw)
In-Reply-To: <20191211092741.totwucrkversjbav@gondor.apana.org.au>

On 11/12/2019 10:27, Herbert Xu wrote:
> On Wed, Dec 11, 2019 at 09:53:56AM +0100, Neil Armstrong wrote:
>>
>> On 11/12/2019 09:41, Anand Moon wrote:
>>> [sudo] password for alarm:
>>> [  903.867059] tcrypt:
>>> [  903.867059] testing speed of async ecb(aes) (ecb(aes-arm64)) encryption
>>
>> Wow, I'm surprised it works on GXBB, Amlogic completely removed HW crypto for GXBB in all their
>> vendor BSPs, in Linux, U-Boot and ATF chain.
>>
>> Could you run more tests to be sure it's really functional ?
> 
> Well as you can see from the tcrypt output, it's actually using
> aes-arm64 which is certainly not the amlogic driver.  Presumably
> the amlogic driver failed to load/register.

Nice catch... thanks Herbert.

Neil

> 
> Cheers,
> 


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2019-12-11  9:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11  8:41 Anand Moon
2019-12-11  8:41 ` [PATCHv1 1/3] arm64: dts: amlogic: adds crypto hardware node for GXBB SoCs Anand Moon
2019-12-11 10:41   ` Anand Moon
2019-12-11  8:41 ` [PATCHv1 2/3] dt-bindings: crypto: Add compatible string for amlogic GXBB SoC Anand Moon
2019-12-11  8:41 ` [PATCHv1 3/3] crypto: amlogic: Add new " Anand Moon
2019-12-11  8:53 ` [PATCHv1 0/3] Enable crypto module on Amlogic GXBB SoC platform Neil Armstrong
2019-12-11  9:27   ` Herbert Xu
2019-12-11  9:32     ` Neil Armstrong [this message]
2019-12-11 10:05     ` Anand Moon
2019-12-11  9:37   ` Anand Moon
2019-12-11  9:50     ` Herbert Xu
2019-12-11 10:33       ` Anand Moon
2019-12-11 12:15       ` Anand Moon
2019-12-11 12:24         ` Ard Biesheuvel
     [not found]           ` <1229236701.11947072.1576070229564@mail.yahoo.com>
2019-12-11 23:30             ` Martin Blumenstingl
2019-12-12  6:23               ` Anand Moon

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=d2b54743-87da-091e-8d62-288ee29a54b0@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=clabbe@baylibre.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.amoon@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=robh+dt@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

all inboxes | Powered by JetHome®