From: Michel Pollet <michel.pollet@bp.renesas.com>
To: linux-renesas-soc@vger.kernel.org, Simon Horman <horms@verge.net.au>
Cc: phil.edworthy@renesas.com,
Michel Pollet <buserror+upstream@gmail.com>,
Michel Pollet <michel.pollet@bp.renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Sebastian Reichel <sre@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: [PATCH v5 2/6] dt-bindings: reset: renesas,rzn1-reboot: document RZ/N1 reboot driver
Date: Tue, 17 Apr 2018 12:04:17 +0100 [thread overview]
Message-ID: <1523963101-56725-3-git-send-email-michel.pollet@bp.renesas.com> (raw)
In-Reply-To: <1523963101-56725-1-git-send-email-michel.pollet@bp.renesas.com>
The Renesas RZ/N1 Family (Part #R9A06G0xx) requires a driver
as part of the sysctrl MFD to handle rebooting the CA7 cores.
This documents the driver bindings.
Signed-off-by: Michel Pollet <michel.pollet@bp.renesas.com>
---
.../devicetree/bindings/power/renesas,rzn1-reboot.txt | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/renesas,rzn1-reboot.txt
diff --git a/Documentation/devicetree/bindings/power/renesas,rzn1-reboot.txt b/Documentation/devicetree/bindings/power/renesas,rzn1-reboot.txt
new file mode 100644
index 0000000..a553864
--- /dev/null
+++ b/Documentation/devicetree/bindings/power/renesas,rzn1-reboot.txt
@@ -0,0 +1,17 @@
+DT bindings for the Renesas RZ/N1 Reboot Driver
+
+== Reboot Driver Node ==
+
+The reboot driver allows restarting the RZ/N1.
+
+Bindings:
++ Required:
+ compatible = "renesas,r9a06g032-reboot", "renesas,rzn1-reboot";
+
+Example:
+ reboot@4000c120 {
+ compatible = "renesas,r9a06g032-reboot",
+ "renesas,rzn1-reboot";
+ reg = <0x4000c120 4>,
+ <0x4000c198 4>;
+ };
--
2.7.4
next prev parent reply other threads:[~2018-04-17 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 11:04 [PATCH v5 0/8] arm: Base support for Renesas RZN1D-DB Board Michel Pollet
2018-04-17 11:04 ` [PATCH v5 1/6] arm: shmobile: Add the RZ/N1D (R9A06G032) to the shmobile Kconfig Michel Pollet
2018-04-23 10:08 ` Simon Horman
2018-04-17 11:04 ` Michel Pollet [this message]
2018-04-19 9:10 ` [PATCH v5 2/6] dt-bindings: reset: renesas,rzn1-reboot: document RZ/N1 reboot driver Geert Uytterhoeven
2018-04-17 11:04 ` [PATCH v5 3/6] dt-bindings: arm: Document the RZN1D-DB board Michel Pollet
2018-04-17 13:23 ` Rob Herring
2018-04-17 15:49 ` Geert Uytterhoeven
2018-04-23 10:02 ` Simon Horman
2018-04-17 11:04 ` [PATCH v5 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file Michel Pollet
2018-04-23 10:14 ` Simon Horman
2018-04-17 11:04 ` [PATCH v5 5/6] ARM: dts: Renesas RZN1D-DB Board base file Michel Pollet
2018-04-17 11:04 ` [PATCH v5 6/6] reset: Renesas RZ/N1 reboot driver Michel Pollet
2018-04-25 21:37 ` Sebastian Reichel
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=1523963101-56725-3-git-send-email-michel.pollet@bp.renesas.com \
--to=michel.pollet@bp.renesas.com \
--cc=buserror+upstream@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=phil.edworthy@renesas.com \
--cc=robh+dt@kernel.org \
--cc=sre@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).