u-boot-amlogic.groups.io archive mirror
 help / color / mirror / Atom feed
From: Alexey Romanov <avromanov@salutedevices.com>
To: neil.armstrong@linaro.org, narmstrong@baylibre.com
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de,
	kernel@sberdevices.ru,
	Alexey Romanov <avromanov@salutedevices.com>
Subject: [PATCH v2 1/2] meson-a1: dts: add hw rng node
Date: Tue, 10 Oct 2023 13:06:16 +0300	[thread overview]
Message-ID: <20231010100623.74475-2-avromanov@salutedevices.com> (raw)
In-Reply-To: <20231010100623.74475-1-avromanov@salutedevices.com>

Add support for hardware random number generator
of Amlogic Meson SoCs.

Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
---
 arch/arm/dts/meson-a1.dtsi | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/arch/arm/dts/meson-a1.dtsi b/arch/arm/dts/meson-a1.dtsi
index 6509329b85..e6e72d4004 100644
--- a/arch/arm/dts/meson-a1.dtsi
+++ b/arch/arm/dts/meson-a1.dtsi
@@ -124,6 +124,11 @@
 				clock-names = "xtal", "pclk", "baud";
 				status = "disabled";
 			};
+
+			hwrng: rng@5118 {
+				compatible = "amlogic,meson-rng";
+				reg = <0x0 0x5118 0x0 0x4>;
+			};
 		};
 
 		gic: interrupt-controller@ff901000 {
-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Alexey Romanov <avromanov@salutedevices.com>
To: <neil.armstrong@linaro.org>, <narmstrong@baylibre.com>
Cc: <u-boot-amlogic@groups.io>, <u-boot@lists.denx.de>,
	<kernel@sberdevices.ru>,
	Alexey Romanov <avromanov@salutedevices.com>
Subject: [PATCH v2 1/2] meson-a1: dts: add hw rng node
Date: Tue, 10 Oct 2023 13:06:16 +0300	[thread overview]
Message-ID: <20231010100623.74475-2-avromanov@salutedevices.com> (raw)
Message-ID: <20231010100616.ViUK_MjgRgZHqPMzDUz-Npl_uDSGgwtOjMaFNvWpgfM@z> (raw)
In-Reply-To: <20231010100623.74475-1-avromanov@salutedevices.com>

Add support for hardware random number generator
of Amlogic Meson SoCs.

Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
---
 arch/arm/dts/meson-a1.dtsi | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/arch/arm/dts/meson-a1.dtsi b/arch/arm/dts/meson-a1.dtsi
index 6509329b85..e6e72d4004 100644
--- a/arch/arm/dts/meson-a1.dtsi
+++ b/arch/arm/dts/meson-a1.dtsi
@@ -124,6 +124,11 @@
 				clock-names = "xtal", "pclk", "baud";
 				status = "disabled";
 			};
+
+			hwrng: rng@5118 {
+				compatible = "amlogic,meson-rng";
+				reg = <0x0 0x5118 0x0 0x4>;
+			};
 		};
 
 		gic: interrupt-controller@ff901000 {
-- 
2.25.1



  parent reply	other threads:[~2023-10-10 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 10:06 [PATCH v2 0/2] Meson A1: add HW RNG and AO Secure nodes Alexey Romanov
2023-10-10 10:06 ` Alexey Romanov
2023-10-10 10:06 ` Alexey Romanov [this message]
2023-10-10 10:06   ` [PATCH v2 1/2] meson-a1: dts: add hw rng node Alexey Romanov
2023-10-10 10:06 ` [PATCH v2 2/2] meson-a1: dts: add ao secure node Alexey Romanov
2023-10-10 10:06   ` Alexey Romanov
2023-10-15 10:31 ` [PATCH v2 0/2] Meson A1: add HW RNG and AO Secure nodes neil.armstrong

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=20231010100623.74475-2-avromanov@salutedevices.com \
    --to=avromanov@salutedevices.com \
    --cc=kernel@sberdevices.ru \
    --cc=narmstrong@baylibre.com \
    --cc=neil.armstrong@linaro.org \
    --cc=u-boot-amlogic@groups.io \
    --cc=u-boot@lists.denx.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).