From: Scott Wood <scottwood@freescale.com>
To: Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Cc: Wang Dongsheng-B40534 <Dongsheng.Wang@freescale.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Zhao Chenhui-B35336" <chenhui.zhao@freescale.com>,
Wang Huan-B18965 <alison.wang@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Tang Yuantian-B29983 <Yuantian.Tang@freescale.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"Jin Zhengxiong-R64188" <Jason.Jin@freescale.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 1/2] fsl: Add binding for RCPM
Date: Thu, 1 Oct 2015 12:07:44 -0500 [thread overview]
Message-ID: <1443719264.5336.133.camel@freescale.com> (raw)
In-Reply-To: <CY1PR0301MB0748AB1CE2D93FFD79FE6009874C0@CY1PR0301MB0748.namprd03.prod.outlook.com>
On Thu, 2015-10-01 at 12:05 -0500, Yoder Stuart-B08248 wrote:
> > +++ 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.
>
> s/RCPM block/the RCPM block/
>
> > + - fsl,#rcpm-wakeup-cells : The number of cells in rcpm-wakeup property.
>
> s/rcpm-wakeup-property/the rcpm-wakeup-property/
>
> > + - compatible : Sould contain a chip-specific RCPM block compatible
> > string
>
> s/Sould/Should
>
> "Should" means it is recommended, but does not mean "must". Is it really
> optional?
>
> > + 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"
>
> 2 or 3 examples is enough.
>
> > + 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
>
> Not sure this binding is the place to maintain a table of chassis
> versions to SoCs.
This is something I've been encouraging, given that the block versions are
not publicly documented. It lets people find a manual that describes the
advertised programming interface.
-Scott
next prev parent reply other threads:[~2015-10-01 17:08 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 ` [PATCH v3 1/2] fsl: Add binding for RCPM Shawn Guo
2015-09-25 2:24 ` 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 [this message]
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=1443719264.5336.133.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Dongsheng.Wang@freescale.com \
--cc=Jason.Jin@freescale.com \
--cc=Yuantian.Tang@freescale.com \
--cc=alison.wang@freescale.com \
--cc=chenhui.zhao@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stuart.yoder@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).