From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
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>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v5 1/7] PM / Domains: Add DT bindings for the R-Car System Controller
Date: Wed, 13 Apr 2016 16:44:17 +0200 [thread overview]
Message-ID: <1460558663-10197-2-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1460558663-10197-1-git-send-email-geert+renesas@glider.be>
The Renesas R-Car System Controller provides power management for the
CPU cores and various coprocessors, following the generic PM domain
bindings in Documentation/devicetree/bindings/power/power_domain.txt.
This supports R-Car Gen1 (H1), Gen2, and Gen3.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Rob Herring <robh@kernel.org>
---
v5:
- Remove power-domains property from the sysc node again, as the
System Controller itself is not part of the Clock Domain,
v4:
- Add Reviewed-by, Acked-by,
- Compatible value must contain "exactly one" instead of "one or
more",
- Add power-domains property to refer to the SoC's Clock Domain,
v3:
- Move power area hierarchy from DT to C (cfr. DT bindings for Renesas
CPG/MSSR), and switch to "#power-domain-cells = <1>",
- Drop fallback compatibility strings, as the bindings are
SoC-specific,
- Rename from renesas,sysc-rcar.txt to renesas,rcar-sysc.txt,
v2:
- Add R-Car H3 (r8a7795) support,
- Use "renesas,<type>-sysc" instead of "renesas,sysc-<type>",
- Add fallback compatibility strings for R-Car Gen2 and Gen3.
---
.../bindings/power/renesas,rcar-sysc.txt | 48 ++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt
diff --git a/Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt b/Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt
new file mode 100644
index 0000000000000000..b74e4d4785ab2d60
--- /dev/null
+++ b/Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt
@@ -0,0 +1,48 @@
+DT bindings for the Renesas R-Car System Controller
+
+== System Controller Node ==
+
+The R-Car System Controller provides power management for the CPU cores and
+various coprocessors.
+
+Required properties:
+ - compatible: Must contain exactly one of the following:
+ - "renesas,r8a7779-sysc" (R-Car H1)
+ - "renesas,r8a7790-sysc" (R-Car H2)
+ - "renesas,r8a7791-sysc" (R-Car M2-W)
+ - "renesas,r8a7792-sysc" (R-Car V2H)
+ - "renesas,r8a7793-sysc" (R-Car M2-N)
+ - "renesas,r8a7794-sysc" (R-Car E2)
+ - "renesas,r8a7795-sysc" (R-Car H3)
+ - reg: Address start and address range for the device.
+ - #power-domain-cells: Must be 1.
+
+
+Example:
+
+ sysc: system-controller@e6180000 {
+ compatible = "renesas,r8a7791-sysc";
+ reg = <0 0xe6180000 0 0x0200>;
+ #power-domain-cells = <1>;
+ };
+
+
+== PM Domain Consumers ==
+
+Devices residing in a power area must refer to that power area, as documented
+by the generic PM domain bindings in
+Documentation/devicetree/bindings/power/power_domain.txt.
+
+Required properties:
+ - power-domains: A phandle and symbolic PM domain specifier, as defined in
+ <dt-bindings/power/r8a77*-sysc.h>.
+
+
+Example:
+
+ L2_CA15: cache-controller@0 {
+ compatible = "cache";
+ power-domains = <&sysc R8A7791_PD_CA15_SCU>;
+ cache-unified;
+ cache-level = <2>;
+ };
--
1.9.1
next prev parent reply other threads:[~2016-04-13 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 14:44 [PATCH v5 0/7] PM / Domains: Add DT bindings for the R-Car System Controller Geert Uytterhoeven
2016-04-13 14:44 ` Geert Uytterhoeven [this message]
2016-04-13 14:44 ` [PATCH v5 2/7] soc: renesas: Add r8a7779 SYSC PM Domain Binding Definitions Geert Uytterhoeven
[not found] ` <1460558663-10197-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2016-04-13 14:44 ` [PATCH v5 3/7] soc: renesas: Add r8a7790 " Geert Uytterhoeven
2016-04-13 14:44 ` [PATCH v5 4/7] soc: renesas: Add r8a7791 " Geert Uytterhoeven
2016-04-13 14:44 ` [PATCH v5 5/7] soc: renesas: Add r8a7793 " Geert Uytterhoeven
2016-04-13 14:44 ` [PATCH v5 6/7] soc: renesas: Add r8a7794 " Geert Uytterhoeven
2016-04-13 14:44 ` [PATCH v5 7/7] soc: renesas: Add r8a7795 " Geert Uytterhoeven
2016-04-15 1:04 ` [PATCH v5 0/7] PM / Domains: Add DT bindings for the R-Car System Controller Simon Horman
[not found] ` <20160415010416.GC31938-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2016-04-15 6:37 ` Geert Uytterhoeven
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=1460558663-10197-2-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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).