From: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
To: mpm@selenic.com, herbert@gondor.apana.org.au, robh+dt@kernel.org,
mark.rutland@arm.com, ralf@linux-mips.org,
gregkh@linuxfoundation.org, boris.brezillon@free-electrons.com,
harvey.hunt@imgtec.com, prarit@redhat.com, f.fainelli@gmail.com,
joshua.henderson@microchip.com, narmstrong@baylibre.com,
linus.walleij@linaro.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-mips@linux-mips.org
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Subject: [PATCH v2 3/4] hw_random: jz4780-rng: Add RNG node to jz4780.dtsi
Date: Sat, 27 Aug 2016 23:44:56 +0530 [thread overview]
Message-ID: <1472321697-3094-4-git-send-email-prasannatsmkumar@gmail.com> (raw)
In-Reply-To: <1472321697-3094-1-git-send-email-prasannatsmkumar@gmail.com>
This patch adds RNG node to jz4780.dtsi.
Signed-off-by: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
---
arch/mips/boot/dts/ingenic/jz4780.dtsi | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/mips/boot/dts/ingenic/jz4780.dtsi b/arch/mips/boot/dts/ingenic/jz4780.dtsi
index b868b42..f11d139 100644
--- a/arch/mips/boot/dts/ingenic/jz4780.dtsi
+++ b/arch/mips/boot/dts/ingenic/jz4780.dtsi
@@ -36,7 +36,7 @@
cgu: jz4780-cgu@10000000 {
compatible = "ingenic,jz4780-cgu";
- reg = <0x10000000 0x100>;
+ reg = <0x10000000 0xD8>;
clocks = <&ext>, <&rtc>;
clock-names = "ext", "rtc";
@@ -44,6 +44,11 @@
#clock-cells = <1>;
};
+ rng: jz4780-rng@100000D8 {
+ compatible = "ingenic,jz4780-rng";
+ reg = <0x100000D8 0x8>;
+ };
+
uart0: serial@10030000 {
compatible = "ingenic,jz4780-uart";
reg = <0x10030000 0x100>;
--
2.5.0
next prev parent reply other threads:[~2016-08-27 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 18:14 [PATCH v2 0/4] hw_random: Add driver for Ingenic JZ4780 SoC RNG PrasannaKumar Muralidharan
2016-08-27 18:14 ` [PATCH v2 2/4] hw_random: jz4780-rng: Add Ingenic JZ4780 hardware RNG driver PrasannaKumar Muralidharan
2016-08-27 18:14 ` PrasannaKumar Muralidharan [this message]
[not found] ` <1472321697-3094-4-git-send-email-prasannatsmkumar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-28 10:33 ` [PATCH v2 3/4] hw_random: jz4780-rng: Add RNG node to jz4780.dtsi Sergei Shtylyov
2016-08-28 17:59 ` PrasannaKumar Muralidharan
2016-09-02 12:47 ` Paul Burton
[not found] ` <4a7fb1cb-e0d4-31b7-7016-35adb63a659d-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2016-09-02 12:57 ` PrasannaKumar Muralidharan
[not found] ` <1472321697-3094-1-git-send-email-prasannatsmkumar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-27 18:14 ` [PATCH v2 1/4] hw_random: jz4780-rng: Add devicetree bindings for RNG in JZ4780 SoC PrasannaKumar Muralidharan
2016-08-27 18:14 ` [PATCH v2 4/4] hw_random: jz4780-rng: Enable hardware RNG in CI20 defconfig PrasannaKumar Muralidharan
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=1472321697-3094-4-git-send-email-prasannatsmkumar@gmail.com \
--to=prasannatsmkumar@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=harvey.hunt@imgtec.com \
--cc=herbert@gondor.apana.org.au \
--cc=joshua.henderson@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=mpm@selenic.com \
--cc=narmstrong@baylibre.com \
--cc=prarit@redhat.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).