From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: barebox@lists.infradead.org
Cc: Alexander Shiyan <eagle.alexander923@gmail.com>
Subject: [PATCH v2] ARM: dts: rk356x: Use RNG node from upstream DTSI
Date: Thu, 12 Dec 2024 09:43:03 +0300 [thread overview]
Message-ID: <20241212064303.8765-1-eagle.alexander923@gmail.com> (raw)
Since the RNG node was added to the upstream DTSI, let's reuse it.
This change disables HWRNG on RK3566, as done in the kernel[1].
[1]: https://lore.kernel.org/all/302bdae2f4defeefe88ea4018a0be11f@manjaro.org/
Signed-off-by: Alexander Shiyan <eagle.alexander923@gmail.com>
---
arch/arm/dts/rk356x.dtsi | 8 --------
drivers/hw_random/rockchip-rng.c | 2 +-
2 files changed, 1 insertion(+), 9 deletions(-)
diff --git a/arch/arm/dts/rk356x.dtsi b/arch/arm/dts/rk356x.dtsi
index fbabf2a6a6..995a9d5d92 100644
--- a/arch/arm/dts/rk356x.dtsi
+++ b/arch/arm/dts/rk356x.dtsi
@@ -44,14 +44,6 @@ cpu_id: id@a {
reg = <0x0a 0x10>;
};
};
-
- rng: rng@fe388000 {
- compatible = "rockchip,rk3568-rng", "rockchip,cryptov2-rng";
- reg = <0x0 0xfe388000 0x0 0x2000>;
- clocks = <&cru CLK_TRNG_NS>, <&cru HCLK_TRNG_NS>;
- clock-names = "trng_clk", "trng_hclk";
- resets = <&cru SRST_TRNG_NS>;
- };
};
&pmugrf {
diff --git a/drivers/hw_random/rockchip-rng.c b/drivers/hw_random/rockchip-rng.c
index 990e5fc111..62a21db0e2 100644
--- a/drivers/hw_random/rockchip-rng.c
+++ b/drivers/hw_random/rockchip-rng.c
@@ -194,7 +194,7 @@ static const struct of_device_id rk_rng_dt_match[] = {
.data = (void *)&rk_rng_v1_soc_data,
},
{
- .compatible = "rockchip,cryptov2-rng",
+ .compatible = "rockchip,rk3568-rng",
.data = (void *)&rk_rng_v2_soc_data,
},
{ },
--
2.39.1
next reply other threads:[~2024-12-12 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 6:43 Alexander Shiyan [this message]
2024-12-12 8:25 ` Sascha Hauer
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=20241212064303.8765-1-eagle.alexander923@gmail.com \
--to=eagle.alexander923@gmail.com \
--cc=barebox@lists.infradead.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