From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, Dragan Simic <dsimic@manjaro.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
didi.debian@cknow.org, marcin.juszkiewicz@linaro.org
Subject: Re: [PATCH] arm64: dts: rockchip: Describe why is HWRNG disabled in RK356x base dtsi
Date: Mon, 3 Feb 2025 09:15:55 +0100 [thread overview]
Message-ID: <173857053622.78657.16352325923556757290.b4-ty@sntech.de> (raw)
In-Reply-To: <6b272e2f8f916c04b05db50df621659a5a7f29ab.1733149874.git.dsimic@manjaro.org>
On Mon, 02 Dec 2024 15:44:06 +0100, Dragan Simic wrote:
> Despite the presence of the hardware random number generator (HWRNG) in the
> different Rockchip RK356x SoC variants, it remains disabled for the RK3566
> SoC because testing showed [1] that it produces unacceptably low quality of
> random data, for some yet unknown reason. The HWRNG is enabled for the RK3568
> SoC, on which the testing showed good quality of the generated random data.
>
> To avoid possible confusion in the future, [2] let's have this described
> briefly in the RK356x base SoC dtsi.
>
> [...]
Applied, thanks!
[1/1] arm64: dts: rockchip: Describe why is HWRNG disabled in RK356x base dtsi
commit: 5afdb98dcc55917df4a8568fd07a119844a7d391
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2025-02-03 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 14:44 Dragan Simic
2024-12-02 14:55 ` Dragan Simic
2024-12-02 17:05 ` Diederik de Haas
2024-12-02 18:33 ` Dragan Simic
2025-01-15 9:51 ` Dragan Simic
2025-02-03 8:15 ` Heiko Stuebner [this message]
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=173857053622.78657.16352325923556757290.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dsimic@manjaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=robh@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®