devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dong Aisheng <aisheng.dong@nxp.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
	Mark Rutland <mark.rutland@arm.com>,
	ulf.hansson@linaro.org, dongas86@gmail.com, khilman@kernel.org,
	linux-pm@vger.kernel.org, rjw@rjwysocki.net,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	linux-imx@nxp.com, kernel@pengutronix.de, fabio.estevam@nxp.com,
	shawnguo@kernel.org
Subject: [PATCH 1/2] dt-bindings: power: add i.MX SCU power domains binding doc
Date: Sat, 28 Apr 2018 02:51:02 +0800	[thread overview]
Message-ID: <1524855063-14996-2-git-send-email-aisheng.dong@nxp.com> (raw)
In-Reply-To: <1524855063-14996-1-git-send-email-aisheng.dong@nxp.com>

Some i.MX SoCs contain a system controller that is responsible for
controlling the state of the IPs that are present.
Communication between the host processor running an OS and the system
controller happens through a SCU protocol.

Cc: Shawn Guo <shawnguo@kernel.org>
Cc: Sascha Hauer <kernel@pengutronix.de>
Cc: Fabio Estevam <fabio.estevam@nxp.com>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org
Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
---
 .../devicetree/bindings/power/nxp,imx-pd-scu.txt   | 84 ++++++++++++++++++++++
 1 file changed, 84 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/power/nxp,imx-pd-scu.txt

diff --git a/Documentation/devicetree/bindings/power/nxp,imx-pd-scu.txt b/Documentation/devicetree/bindings/power/nxp,imx-pd-scu.txt
new file mode 100644
index 0000000..d21cc22
--- /dev/null
+++ b/Documentation/devicetree/bindings/power/nxp,imx-pd-scu.txt
@@ -0,0 +1,84 @@
+NXP i.MX Power Domain Based on SCFW
+--------------------------------------------------------------------
+
+Some i.MX SoCs contain a system controller that is responsible for
+controlling the state of the IPs that are present.
+Communication between the host processor running an OS and the system
+controller happens through a SCU protocol [1].
+
+[1] Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt
+
+Required Properties:
+--------------------
+- compatible:		should be "nxp,<soc>-pd".
+			Supported SoCs: imx8qxp and imx8qm.
+- #power-domain-cells:	Must be 0
+- #address-cells:	Should be 1.
+- #size-cells:		Should be 0.
+
+Optional Properties:
+- reg:			Resource ID of this power domain.
+			No exist means uncontrollable by user.
+			See detailed Resource ID list from:
+			include/dt-bindings/power/imx-rsrc.h
+
+Required properties for power domain sub nodes:
+- reg:			Resource ID of this power domain.
+- #power-domain-cells:	Must be 0
+- power-domains:	phandle pointing to the parent power domain,
+			for more details see:
+			Documentation/devicetree/bindings/power/power_domain.txt
+
+Example:
+-------------
+	scu {
+		compatible = "nxp,imx8qxp-scu";
+		fsl,mu = <&lsio_mu0>;
+		status = "okay";
+
+		pd_lsio: lsio_power_domain {
+			compatible = "nxp,imx8qxp-pd";
+			#power-domain-cells = <0>;
+			#address-cells = <1>;
+			#size-cells = <0>;
+
+			pd_lsio_pwm0: lsio_pwm0@SC_R_PWM_0 {
+				reg = <SC_R_PWM_0>;
+				#power-domain-cells = <0>;
+				power-domains = <&pd_lsio>;
+			};
+			...
+		}
+
+		pd_dma: dma_power_domain {
+			compatible = "nxp,imx8-pd";
+			#power-domain-cells = <0>;
+			#address-cells = <1>;
+			#size-cells = <0>;
+
+			pd_dma_lpuart0: dma_lpuart0@SC_R_UART_0 {
+				reg = <SC_R_UART_0>;
+				#power-domain-cells = <0>;
+				power-domains = <&pd_dma>;
+			};
+			...
+		}
+		...
+	};
+
+PM Domain Consumers
+===================
+Hardware blocks belonging to a PM domain should contain a "power-domains"
+property that is a phandle pointing to the corresponding PM domain node.
+
+Required Properties:
+--------------------
+- power-domains: phandle pointing to the corresponding PM domain node.
+
+Example:
+--------------------
+	lpuart0: serial@5a060000 {
+		compatible = "fsl,imx8qxp-lpuart";
+		....
+		power-domains = <&pd_dma_lpuart0>;
+	};
-- 
2.7.4

           reply	other threads:[~2018-04-27 18:51 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1524855063-14996-1-git-send-email-aisheng.dong@nxp.com>]

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=1524855063-14996-2-git-send-email-aisheng.dong@nxp.com \
    --to=aisheng.dong@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dongas86@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@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).