From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sohaib Mohamed <sohaib.amhmd@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 10/14] rockchip-rng: Add RK3562 support
Date: Fri, 30 Jan 2026 09:02:41 +0100 [thread overview]
Message-ID: <d623c35c-e2d9-4697-8d7f-984dfdf49399@pengutronix.de> (raw)
In-Reply-To: <20260130-barebox-kickpi-v2-10-d27cf94a39b6@gmail.com>
On 1/30/26 06:17, Sohaib Mohamed wrote:
> Add compatible string for RK3562 RNG support.
Nitpick: I'd have rather suggested hw_random as prefix, but I don't think
you need to resend just for that.
>
> Signed-off-by: Sohaib Mohamed <sohaib.amhmd@gmail.com>
Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> drivers/hw_random/rockchip-rng.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/hw_random/rockchip-rng.c b/drivers/hw_random/rockchip-rng.c
> index 8856a3883e..f1f4c4cb12 100644
> --- a/drivers/hw_random/rockchip-rng.c
> +++ b/drivers/hw_random/rockchip-rng.c
> @@ -193,6 +193,10 @@ static const struct of_device_id rk_rng_dt_match[] = {
> .compatible = "rockchip,cryptov1-rng",
> .data = &rk_rng_v1_soc_data,
> },
> + {
> + .compatible = "rockchip,rk3562-rng",
> + .data = &rk_rng_v2_soc_data,
> + },
> {
> .compatible = "rockchip,rk3568-rng",
> .data = &rk_rng_v2_soc_data,
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-01-30 8:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 5:16 [PATCH v2 00/14] ARM: rockchip: Add initial RK3562 SoC support Sohaib Mohamed
2026-01-30 5:16 ` [PATCH v2 01/14] " Sohaib Mohamed
2026-01-30 5:16 ` [PATCH v2 02/14] clk: rockchip: add RK3562 clock and reset driver support Sohaib Mohamed
2026-01-30 5:16 ` [PATCH v2 03/14] pinctrl: rockchip: sync driver with Linux Sohaib Mohamed
2026-01-30 5:16 ` [PATCH v2 04/14] ARM: boards: Rockchip: add RK3562-EVB2 support Sohaib Mohamed
2026-01-30 5:16 ` [PATCH v2 05/14] ARM: boards: Rockchip: Add device tree for kickpi k3 board Sohaib Mohamed
2026-01-30 5:16 ` [PATCH v2 06/14] ARM: rockchip: Add RK3562 KickPi K3 board support Sohaib Mohamed
2026-01-30 5:16 ` [PATCH v2 07/14] pmdomain: rockchip: Add RK3562 power domain support Sohaib Mohamed
2026-01-30 8:00 ` Ahmad Fatoum
2026-01-30 5:17 ` [PATCH v2 08/14] aiodev: rockchip_saradc: Add RK3562 support Sohaib Mohamed
2026-01-30 8:01 ` Ahmad Fatoum
2026-01-30 5:17 ` [PATCH v2 09/14] phy: rockchip-inno-usb2: Add support for RK3562 PHY Sohaib Mohamed
2026-01-30 8:01 ` Ahmad Fatoum
2026-01-30 5:17 ` [PATCH v2 10/14] rockchip-rng: Add RK3562 support Sohaib Mohamed
2026-01-30 8:02 ` Ahmad Fatoum [this message]
2026-01-30 5:17 ` [PATCH v2 11/14] mci: sdhci: rockchip-dwcmshc: " Sohaib Mohamed
2026-01-30 8:03 ` Ahmad Fatoum
2026-01-30 5:17 ` [PATCH v2 12/14] nvmem: rockchip-otp: " Sohaib Mohamed
2026-01-30 8:03 ` Ahmad Fatoum
2026-01-30 5:17 ` [PATCH v2 13/14] phy: rockchip: inno-dsidphy: " Sohaib Mohamed
2026-01-30 8:04 ` Ahmad Fatoum
2026-01-30 5:17 ` [PATCH v2 14/14] phy: rockchip: naneng-combphy: " Sohaib Mohamed
2026-01-30 8:05 ` Ahmad Fatoum
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=d623c35c-e2d9-4697-8d7f-984dfdf49399@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=sohaib.amhmd@gmail.com \
/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