From: "Heiko Stübner" <heiko@sntech.de>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
krzysztof.kozlowski+dt@linaro.org, mturquette@baylibre.com,
p.zabel@pengutronix.de, robh+dt@kernel.org, sboyd@kernel.org,
Corentin Labbe <clabbe@baylibre.com>
Cc: ricardo@pardini.net, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Corentin Labbe <clabbe@baylibre.com>
Subject: Re: [PATCH 4/6] ARM64: dts: rk356x: add crypto node
Date: Tue, 07 Nov 2023 17:00:10 +0100 [thread overview]
Message-ID: <4334358.iZASKD2KPV@diego> (raw)
In-Reply-To: <20231107155532.3747113-5-clabbe@baylibre.com>
Am Dienstag, 7. November 2023, 16:55:30 CET schrieb Corentin Labbe:
> Both RK3566 and RK3568 have a crypto IP handled by the rk3588 crypto driver so adds a
> node for it.
please follow other commits in the subject line, i.e.:
"arm64: dts: rockchip: add rk356x crypto node"
Thanks
Heiko
>
> Tested-by: Ricardo Pardini <ricardo@pardini.net>
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> ---
> arch/arm64/boot/dts/rockchip/rk356x.dtsi | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> index 0964761e3ce9..c94a1b535c32 100644
> --- a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> @@ -1070,6 +1070,18 @@ sdhci: mmc@fe310000 {
> status = "disabled";
> };
>
> + crypto: crypto@fe380000 {
> + compatible = "rockchip,rk3568-crypto";
> + reg = <0x0 0xfe380000 0x0 0x2000>;
> + interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru ACLK_CRYPTO_NS>, <&cru HCLK_CRYPTO_NS>,
> + <&cru CLK_CRYPTO_NS_CORE>;
> + clock-names = "aclk", "hclk", "core";
> + resets = <&cru SRST_CRYPTO_NS_CORE>;
> + reset-names = "core";
> + status = "okay";
> + };
> +
> i2s0_8ch: i2s@fe400000 {
> compatible = "rockchip,rk3568-i2s-tdm";
> reg = <0x0 0xfe400000 0x0 0x1000>;
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-11-07 16:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 15:55 [PATCH 0/6] crypto: rockchip: add support for rk3588/rk3568 Corentin Labbe
2023-11-07 15:55 ` [PATCH 1/6] dt-bindings: crypto: add support for rockchip,crypto-rk3588 Corentin Labbe
2023-11-07 16:40 ` Krzysztof Kozlowski
2023-11-20 12:37 ` Corentin LABBE
2023-11-21 9:04 ` Krzysztof Kozlowski
2023-11-07 15:55 ` [PATCH 2/6] MAINTAINERS: add new dt-binding doc to the right entry Corentin Labbe
2023-11-07 16:20 ` Krzysztof Kozlowski
2023-11-20 12:37 ` Corentin LABBE
2023-11-07 15:55 ` [PATCH 3/6] ARM64: dts: rk3588: add crypto node Corentin Labbe
2023-11-07 15:59 ` Heiko Stübner
2023-11-20 12:38 ` Corentin LABBE
2023-11-07 16:20 ` Krzysztof Kozlowski
2023-11-20 12:38 ` Corentin LABBE
2023-11-07 15:55 ` [PATCH 4/6] ARM64: dts: rk356x: " Corentin Labbe
2023-11-07 16:00 ` Heiko Stübner [this message]
2023-11-07 16:21 ` Krzysztof Kozlowski
2023-11-07 15:55 ` [PATCH 5/6] reset: rockchip: secure reset must be used by SCMI Corentin Labbe
2023-11-07 16:21 ` Krzysztof Kozlowski
2023-11-07 17:35 ` Heiko Stübner
2023-11-07 17:45 ` Krzysztof Kozlowski
2023-11-11 20:51 ` Sebastian Reichel
2023-11-11 21:28 ` Krzysztof Kozlowski
2023-11-12 20:26 ` Sebastian Reichel
2023-11-20 12:42 ` Corentin LABBE
2023-11-07 15:55 ` [PATCH 6/6] crypto: rockchip: add rk3588 driver Corentin Labbe
2023-11-07 16:35 ` Krzysztof Kozlowski
2023-11-07 16:42 ` Krzysztof Kozlowski
2023-11-07 16:56 ` Krzysztof Kozlowski
2023-11-12 14:04 ` Aw: " Frank Wunderlich
2023-11-20 12:48 ` Corentin LABBE
2023-11-24 15:05 ` Aw: " Frank Wunderlich
2023-11-27 11:47 ` Corentin LABBE
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=4334358.iZASKD2KPV@diego \
--to=heiko@sntech.de \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=ricardo@pardini.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).