From: Anup Patel <anup.patel@broadcom.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vikram Prakash <vikramp@broadcom.com>,
Anup Patel <anup.patel@broadcom.com>,
Pramod KUMAR <pramodku@broadcom.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH 3/6] arm64: dts: Add syscon based reboot in DT for NS2
Date: Fri, 2 Oct 2015 23:24:20 +0530 [thread overview]
Message-ID: <1443808463-21120-4-git-send-email-anup.patel@broadcom.com> (raw)
In-Reply-To: <1443808463-21120-1-git-send-email-anup.patel@broadcom.com>
To reset NS2, we simply have to write '0' to BIT[1] at offset 0x90
of CRMU space.
The above can be easily achieved by writing 0xfffffffd at offset 0x90
using syscon-reboot driver. We don't need to have separate driver for
rebooting NS2.
This patch enables syscon-reboot driver for NS2 using DT.
Signed-off-by: Anup Patel <anup.patel@broadcom.com>
Reviewed-by: Ray Jui <rjui@broadcom.com>
Reviewed-by: Scott Branden <sbranden@broadcom.com>
---
arch/arm64/boot/dts/broadcom/ns2.dtsi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/broadcom/ns2.dtsi b/arch/arm64/boot/dts/broadcom/ns2.dtsi
index c5d90e4..5d2ac6b 100644
--- a/arch/arm64/boot/dts/broadcom/ns2.dtsi
+++ b/arch/arm64/boot/dts/broadcom/ns2.dtsi
@@ -144,6 +144,18 @@
mmu-masters;
};
+ crmu: crmu@65024000 {
+ compatible = "syscon";
+ reg = <0x65024000 0x100>;
+ };
+
+ reboot@65024000 {
+ compatible ="syscon-reboot";
+ regmap = <&crmu>;
+ offset = <0x90>;
+ mask = <0xfffffffd>;
+ };
+
gic: interrupt-controller@65210000 {
compatible = "arm,gic-400";
#interrupt-cells = <3>;
--
1.9.1
next prev parent reply other threads:[~2015-10-02 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 17:54 [PATCH 0/6] arm64: Simple additions to NS2 DT Anup Patel
2015-10-02 17:54 ` [PATCH 1/6] arm64: dts: Add L2-cache DT node for NS2 Anup Patel
2015-10-02 17:54 ` [PATCH 2/6] arm64: dts: Add SMMU " Anup Patel
2015-10-02 17:54 ` Anup Patel [this message]
[not found] ` <1443808463-21120-1-git-send-email-anup.patel-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-10-02 17:54 ` [PATCH 4/6] arm64: dts: Add ARM PMUv3 DT node in NS2 DT Anup Patel
2015-10-02 17:54 ` [PATCH 5/6] arm64: dts: Add IPROC RNG200 DT node for NS2 Anup Patel
2015-10-02 17:54 ` [PATCH 6/6] arm64: dts: Add I2C nodes " Anup Patel
2015-10-23 9:19 ` [PATCH 0/6] arm64: Simple additions to NS2 DT Anup Patel
2015-11-03 8:10 ` Anup Patel
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=1443808463-21120-4-git-send-email-anup.patel@broadcom.com \
--to=anup.patel@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=pramodku@broadcom.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=vikramp@broadcom.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).