From: Scott Wood <scottwood@freescale.com>
To: Dongsheng Wang <dongsheng.wang@freescale.com>
Cc: <devicetree@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
<jason.jin@freescale.com>, <chenhui.zhao@freescale.com>,
<yuantian.tang@freescale.com>, <alison.wang@freescale.com>,
<robh+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] fsl: Add binding for RCPM
Date: Wed, 9 Sep 2015 14:56:39 -0500 [thread overview]
Message-ID: <1441828599.29081.36.camel@freescale.com> (raw)
In-Reply-To: <1441780967-30879-1-git-send-email-dongsheng.wang@freescale.com>
On Wed, 2015-09-09 at 14:42 +0800, Dongsheng Wang wrote:
> From: Wang Dongsheng <dongsheng.wang@freescale.com>
>
> RCPM is the Run Control and Power Management module performs all
> device-level tasks associated with device run control and power
> management.
>
> Add this for freescale powerpc platform and layerscape platform.
>
> Signed-off-by: Chenhui Zhao <chenhui.zhao@freescale.com>
> Signed-off-by: Tang Yuantian <Yuantian.Tang@freescale.com>
> Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
>
> diff --git a/Documentation/devicetree/bindings/soc/fsl/rcpm.txt
> b/Documentation/devicetree/bindings/soc/fsl/rcpm.txt
> new file mode 100644
> index 0000000..284070c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/fsl/rcpm.txt
> @@ -0,0 +1,64 @@
> +* Run Control and Power Management
> +-------------------------------------------
> +The RCPM performs all device-level tasks associated with device run control
> +and power management.
> +
> +Required properites:
> + - reg : Offset and length of the register set of RCPM block.
> + - compatible : Sould contain a chip-specific RCPM block compatible string
> + and (if applicable) may contain a chassis-version RCPM compatible string.
> + Chip-specific strings are of the form "fsl,<chip>-rcpm", such as:
> + * "fsl,p2041-rcpm"
> + * "fsl,p3041-rcpm"
> + * "fsl,p4080-rcpm"
> + * "fsl,p5020-rcpm"
> + * "fsl,p5040-rcpm"
> + * "fsl,t4240-rcpm"
> + * "fsl,b4420-rcpm"
> + * "fsl,b4860-rcpm"
> +
> + Chassis-version strings are of the form "fsl,qoriq-rcpm-<version>",
> + such as:
> + * "fsl,qoriq-rcpm-1.0": for chassis 1.0 rcpm
> + * "fsl,qoriq-rcpm-2.0": for chassis 2.0 rcpm
> + * "fsl,qoriq-rcpm-2.1": for chassis 2.1 rcpm
> +
> +All references to "1.0" and "2.0" refer to the QorIQ chassis version to
> +which the chip complies.
> +Chassis Version Example Chips
> +--------------- -------------------------------
> +1.0 p4080, p5020, p5040, p2041, p3041
> +2.0 t4240, b4860, b4420
> +2.1 t1040, ls1021
> +
> +Example:
> +The RCPM node for T4240:
> + rcpm: global-utilities@e2000{
> + compatible = "fsl,t4240-rcpm", "fsl,qoriq-rcpm-2.0";
> + reg = <0xe2000 0x1000>;
> + };
> +
> +The RCPM node for P4080:
> + rcpm: global-utilities@e2000{
> + compatible = "fsl,qoriq-rcpm-1.0";
> + reg = <0xe2000 0x1000>;
> + };
I would avoid putting the p4080 example in the binding, as we don't want to
make it look like it's OK to leave out the specific chip compatible.
> +* Freescale RCPM Wakeup Source Device Tree Bindings
> +-------------------------------------------
> +Required rcpm-wakeup property should be added to a device node if the
> device
> +can be used as a wakeup source.
> +
> + - rcpm-wakeup: should contain a pointer to the rcpm node and the
> + corresponding bit of device in the register.
The corresponding bit in *what* register?
-Scott
next prev parent reply other threads:[~2015-09-09 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 6:42 [PATCH 1/2] fsl: Add binding for RCPM Dongsheng Wang
2015-09-09 6:42 ` [PATCH 2/2] arm/layerscape: add RCPM device tree support for ls1021a Dongsheng Wang
2015-09-09 19:56 ` Scott Wood [this message]
2015-09-10 2:03 ` [PATCH 1/2] fsl: Add binding for RCPM Wang Dongsheng
2015-09-10 16:46 ` Scott Wood
2015-09-11 3:19 ` Wang Dongsheng
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=1441828599.29081.36.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=alison.wang@freescale.com \
--cc=chenhui.zhao@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.wang@freescale.com \
--cc=jason.jin@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=yuantian.tang@freescale.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).