From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Sergey Kuzminov <kuzminov.sergey81@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] board/friendlyarm/nanopi-r3s: rk3566-nanopi-r3s.dts: enable hw random
Date: Wed, 26 Feb 2025 07:26:32 +0200 [thread overview]
Message-ID: <87zfi9e0on.fsf@tarshish> (raw)
In-Reply-To: <20250225174304.1810-1-kuzminov.sergey81@gmail.com> (Sergey Kuzminov's message of "Tue, 25 Feb 2025 20:43:04 +0300")
Hi Sergey,
On Tue, Feb 25 2025, Sergey Kuzminov wrote:
> This patch enables the hardware random number generator in the device tree.
> Without it, the entropy level in the Linux kernel increases very slowly.
> To check the entropy level: cat /proc/sys/kernel/random/entropy_avail
>
> Signed-off-by: Sergey Kuzminov <kuzminov.sergey81@gmail.com>
> ---
> ...001-rk3566-nanopi-r3s.dts-enable-rng.patch | 30 +++++++++++++++++++
> 1 file changed, 30 insertions(+)
> create mode 100644 board/friendlyarm/nanopi-r3s/patches/linux/0001-rk3566-nanopi-r3s.dts-enable-rng.patch
>
> diff --git
> a/board/friendlyarm/nanopi-r3s/patches/linux/0001-rk3566-nanopi-r3s.dts-enable-rng.patch
> b/board/friendlyarm/nanopi-r3s/patches/linux/0001-rk3566-nanopi-r3s.dts-enable-rng.patch
> new file mode 100644
> index 0000000000..b376004377
> --- /dev/null
> +++ b/board/friendlyarm/nanopi-r3s/patches/linux/0001-rk3566-nanopi-r3s.dts-enable-rng.patch
> @@ -0,0 +1,30 @@
> +From 284e6683b4a0ee6b1fd22ccd34785e1f2d58c115 Mon Sep 17 00:00:00 2001
> +From: Sergey Kuzminov <kuzminov.sergey81@gmail.com>
> +Date: Tue, 25 Feb 2025 19:49:00 +0300
> +Subject: [PATCH] rk3566-nanopi-r3s.dts: enable rng
> +
> +This patch enables the hardware random number generator in the device tree.
> +Without it, the entropy level in the Linux kernel increases very slowly.
> +To check the entropy level: cat /proc/sys/kernel/random/entropy_avail
> +
> +Signed-off-by: Sergey Kuzminov <kuzminov.sergey81@gmail.com>
> +Upstream: Not applicable, Buildroot specific.
What makes this patch Buildroot specific?
baruch
> +---
> + arch/arm64/boot/dts/rockchip/rk3566-nanopi-r3s.dts | 4 ++++
> + 1 file changed, 4 insertions(+)
> +
> +diff --git a/arch/arm64/boot/dts/rockchip/rk3566-nanopi-r3s.dts b/arch/arm64/boot/dts/rockchip/rk3566-nanopi-r3s.dts
> +index fb1f65c86883..a89bdbf71e12 100644
> +--- a/arch/arm64/boot/dts/rockchip/rk3566-nanopi-r3s.dts
> ++++ b/arch/arm64/boot/dts/rockchip/rk3566-nanopi-r3s.dts
> +@@ -552,3 +552,7 @@ &vop {
> + &vop_mmu {
> + status = "okay";
> + };
> ++
> ++&rng {
> ++ status = "okay";
> ++};
> +--
> +2.45.3
> +
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-26 5:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 17:43 [Buildroot] [PATCH] board/friendlyarm/nanopi-r3s: rk3566-nanopi-r3s.dts: enable hw random Sergey Kuzminov
2025-02-26 5:26 ` Baruch Siach via buildroot [this message]
2025-02-26 16:51 ` Sergey Kuzminov
[not found] <CAGmsXdzOtEvjSvCe63_B4FScwUO5GK-V+N2hQ1VB0je4-Z+T9g@mail.gmail.com>
2025-02-26 6:17 ` Kuzminov Sergey
2025-02-26 6:35 ` Kuzminov Sergey
2025-02-26 16:44 ` Sergey Kuzminov
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=87zfi9e0on.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=kuzminov.sergey81@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