From: Aurelien Jarno <aurelien@aurel32.net>
To: LABBE Corentin <clabbe@baylibre.com>
Cc: heiko@sntech.de, davem@davemloft.net,
herbert@gondor.apana.org.au, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH RFT 0/5] crypto: rockchip: add crypto offloader V2
Date: Thu, 29 Sep 2022 22:33:29 +0200 [thread overview]
Message-ID: <YzYBGQeaouraFDyo@aurel32.net> (raw)
In-Reply-To: <YzVKR0DjpXT/bB8J@Red>
On 2022-09-29 09:33, LABBE Corentin wrote:
> Le Tue, Sep 27, 2022 at 11:34:58PM +0200, Aurelien Jarno a écrit :
> > On 2022-09-27 08:00, Corentin Labbe wrote:
> > > Hello
> > >
> > > Rockchip rk3568 and rk3588 have a common crypto offloader IP different
> > > than rk3228 one.
> > > I started to work the driver for this IP on a rk3588 based board, but this SoC
> > > is still not upstream.
> > > So it is why I send this serie asking for test since I own no rk3568 and
> > > I need to be sure datasheet is right.
> >
> > I did a quick test, and it doesn't seem to work. I get:
> >
> > rk3588-crypto fe380000.crypto: DMA timeout
> > rk3588-crypto fe380000.crypto: DMA timeout
> >
> > That's on an ODROID-M1 board, so with the set of patches I sent
> > yesterday to support it.
>
> Thanks for testing it, probably I did something wrong because I got a successfull test by someone on #linux-rockchip.
> But I dont know on which board it is, and it was on my debug tree, so probably cleaned something wrong before sending the patchs.
>
> If I sent you a link to my tree, could you retry ?
Yep, I can try that.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-29 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 8:00 [PATCH RFT 0/5] crypto: rockchip: add crypto offloader V2 Corentin Labbe
2022-09-27 8:00 ` [PATCH RFT 1/5] crypto: rockchip: move kconfig to its dedicated directory Corentin Labbe
2022-09-27 8:00 ` [PATCH RFT 2/5] dt-bindings: crypto: add support for rockchip,crypto-rk3588 Corentin Labbe
2022-09-29 22:15 ` Rob Herring
2022-09-27 8:00 ` [PATCH RFT 3/5] MAINTAINERS: add new dt-binding doc to the right entry Corentin Labbe
2022-09-27 8:00 ` [PATCH RFT 4/5] crypto: rockchip: support the new crypto IP for rk3568/rk3588 Corentin Labbe
2022-09-27 21:39 ` Aurelien Jarno
2022-09-29 7:33 ` LABBE Corentin
2022-10-07 4:53 ` Shengyu Qu
2022-09-27 8:00 ` [PATCH RFT 5/5] ARM64: dts: rk3568: add crypto node Corentin Labbe
2022-09-27 21:34 ` [PATCH RFT 0/5] crypto: rockchip: add crypto offloader V2 Aurelien Jarno
2022-09-29 7:33 ` LABBE Corentin
2022-09-29 20:33 ` Aurelien Jarno [this message]
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=YzYBGQeaouraFDyo@aurel32.net \
--to=aurelien@aurel32.net \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).