From: Shawn Guo <shawnguo@kernel•org>
To: Dongsheng Wang <dongsheng.wang@freescale•com>
Cc: scottwood@freescale•com, devicetree@vger•kernel.org,
Chenhui Zhao <chenhui.zhao@freescale•com>,
alison.wang@freescale•com, linuxppc-dev@lists•ozlabs.org,
Tang Yuantian <Yuantian.Tang@freescale•com>,
robh+dt@kernel•org, jason.jin@freescale•com,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v3 1/2] fsl: Add binding for RCPM
Date: Thu, 24 Sep 2015 05:29:17 -0700 [thread overview]
Message-ID: <20150924122917.GQ3529@tiger> (raw)
In-Reply-To: <1443083354-37369-1-git-send-email-dongsheng.wang@freescale.com>
On Thu, Sep 24, 2015 at 04:29:13PM +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>
> ---
> *v3*
> - Add "fsl,#rcpm-wakeup-cells" for rcpm node. The number of cells
> correspond rcpm-wakeup property.
> - Modify rcpm-wakeup property description.
>
> *v2*
> - Remove P4080 example.
> - Modify rcpm-wakeup property description.
>
> diff --git a/Documentation/devicetree/bindings/soc/fsl/rcpm.txt b/Documentation/devicetree/bindings/soc/fsl/rcpm.txt
> new file mode 100644
> index 0000000..52110ec
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/fsl/rcpm.txt
> @@ -0,0 +1,63 @@
> +* 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.
> + - fsl,#rcpm-wakeup-cells : The number of cells in rcpm-wakeup property.
> + - 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>;
> + fsl,#rcpm-wakeup-cells = <2>;
> + };
> +
> +* 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: The value of the property consists of cells, the number of
Shouldn't this vendor specific property be prefixed with 'fsl,' as well?
> + cells defined in "fsl,#rcpm-wakeup-cells". The first cell is a pointer
> + to the rcpm node, the second cell is the bit mask that should be set
> + in IPPDEXPCR0, and the third cell is for IPPDEXPCR1, and so on.
I guess that IPPDEXPCR0 and IPPDEXPCR1 need some documentation too, or a
pointer to hardware documents containing more detailed info about them.
Shawn
> +
> +Example:
> + lpuart0: serial@2950000 {
> + compatible = "fsl,ls1021a-lpuart";
> + reg = <0x0 0x2950000 0x0 0x1000>;
> + interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&sysclk>;
> + clock-names = "ipg";
> + rcpm-wakeup = <&rcpm 0x0 0x40000000>;
> + status = "disabled";
> + };
> --
> 2.1.0.27.g96db324
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists•infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2015-09-24 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 8:29 [PATCH v3 1/2] fsl: Add binding for RCPM Dongsheng Wang
2015-09-24 8:29 ` [PATCH v3 2/2] arm/layerscape: add RCPM device tree support for ls1021a Dongsheng Wang
2015-09-24 12:29 ` Shawn Guo [this message]
2015-09-25 2:24 ` [PATCH v3 1/2] fsl: Add binding for RCPM Wang Dongsheng
2015-09-24 19:30 ` Scott Wood
2015-09-25 2:38 ` Wang Dongsheng
2015-09-25 2:43 ` Scott Wood
2015-09-25 2:51 ` Wang Dongsheng
[not found] ` <CALRxmdDwGgxCG5SfSOaEXK8_fJcG4UUw_9D2=NA7nQhikDyb+A@mail.gmail.com>
2015-10-01 17:05 ` Stuart Yoder
2015-10-01 17:07 ` Scott Wood
2015-10-08 2:32 ` 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=20150924122917.GQ3529@tiger \
--to=shawnguo@kernel$(echo .)org \
--cc=Yuantian.Tang@freescale$(echo .)com \
--cc=alison.wang@freescale$(echo .)com \
--cc=chenhui.zhao@freescale$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=dongsheng.wang@freescale$(echo .)com \
--cc=jason.jin@freescale$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=robh+dt@kernel$(echo .)org \
--cc=scottwood@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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