[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zpz5-2q-C0oQBqoa@zx2c4.com>
Date: Sun, 21 Jul 2024 14:07:23 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Daniel Golle <daniel@...rotopia.org>
Cc: Aurelien Jarno <aurelien@...el32.net>,
Olivia Mackall <olivia@...enic.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Heiko Stuebner <heiko@...ech.de>,
Philipp Zabel <p.zabel@...gutronix.de>,
Dragan Simic <dsimic@...jaro.org>,
Uwe Kleine-König <ukleinek@...ian.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
Martin Kaiser <martin@...ser.cx>,
Francesco Dolcini <francesco.dolcini@...adex.com>,
Ard Biesheuvel <ardb@...nel.org>, linux-crypto@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 3/3] arm64: dts: rockchip: add DT entry for RNG to
RK356x
On Sun, Jul 21, 2024 at 01:48:38AM +0100, Daniel Golle wrote:
> From: Aurelien Jarno <aurelien@...el32.net>
>
> Enable the just added Rockchip RNG driver for RK356x SoCs.
>
> Signed-off-by: Aurelien Jarno <aurelien@...el32.net>
> Signed-off-by: Daniel Golle <daniel@...rotopia.org>
> ---
> arch/arm64/boot/dts/rockchip/rk3568.dtsi | 7 +++++++
> arch/arm64/boot/dts/rockchip/rk356x.dtsi | 10 ++++++++++
> 2 files changed, 17 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3568.dtsi b/arch/arm64/boot/dts/rockchip/rk3568.dtsi
> index f1be76a54ceb..b9c6b2dc87fa 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3568.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3568.dtsi
> @@ -257,6 +257,13 @@ power-domain@...568_PD_PIPE {
> };
> };
>
> +&rng {
> + rockchip,sample-count = <1000>;
> + quality = <900>;
As I already wrote you for v7, quality is out of 1024, not 1000, so this
won't hit 90% as you intend.
But also, I think putting this in the DT is a mistake. Other drivers
don't generally do this, and if the hardware is actually the same piece
to piece (it is...), then there's not per-manufactured unit tweaking
needed. So keep this in the actual driver C like other drivers.
Jason
Powered by blists - more mailing lists