From: Shengyu Qu <wiagn233@outlook.com>
To: clabbe@baylibre.com
Cc: davem@davemloft.net, devicetree@vger.kernel.org, heiko@sntech.de,
herbert@gondor.apana.org.au, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org
Subject: Re: [PATCH RFT 4/5] crypto: rockchip: support the new crypto IP for rk3568/rk3588
Date: Fri, 7 Oct 2022 12:53:42 +0800 [thread overview]
Message-ID: <TY3P286MB261125CD3D2FCB6F390F34D1985F9@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220927080048.3151911-5-clabbe@baylibre.com>
Dear Corentin,
According to official document
(https://github.com/JeffyCN/rockchip_mirrors/blob/docs/Common/CRYPTO/Rockchip_Developer_Guide_Crypto_HWRNG_CN.pdf)
Seems they have just updated downstream source to support more algorithms
such as RSA. So it would be better to sync your code with downstream driver
for more feature.
Shengyu
next prev parent reply other threads:[~2022-10-07 4:54 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 [this message]
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
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=TY3P286MB261125CD3D2FCB6F390F34D1985F9@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM \
--to=wiagn233@outlook.com \
--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
all inboxes | Powered by JetHome®