From: Scott Wood <oss@buserror.net>
To: Ran Wang <ran.wang_1@nxp.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Rob Herring <robh+dt@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Mark Rutland <mark.rutland@arm.com>, Pavel Machek <pavel@ucw.cz>
Cc: Li Biwen <biwen.li@nxp.com>, Len Brown <len.brown@intel.com>,
devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 2/3] Documentation: dt: binding: fsl: Add 'little-endian' and update Chassis define
Date: Thu, 24 Oct 2019 13:33:45 -0500 [thread overview]
Message-ID: <ef150e9eb155eff410194ba5362ef404ce117c4a.camel@buserror.net> (raw)
In-Reply-To: <20191021034927.19300-2-ran.wang_1@nxp.com>
On Mon, 2019-10-21 at 11:49 +0800, Ran Wang wrote:
> By default, QorIQ SoC's RCPM register block is Big Endian. But
> there are some exceptions, such as LS1088A and LS2088A, are
> Little Endian. So add this optional property to help identify
> them.
>
> Actually LS2021A and other Layerscapes won't totally follow Chassis
> 2.1, so separate them from powerpc SoC.
Did you mean LS1021A and "don't" instead of "won't", given the change to the
examples?
> Change in v5:
> - Add 'Reviewed-by: Rob Herring <robh@kernel.org>' to commit message.
> - Rename property 'fsl,#rcpm-wakeup-cells' to '#fsl,rcpm-wakeup-
> cells'.
> please see https://lore.kernel.org/patchwork/patch/1101022/
I'm not sure why Rob considers this the "correct form" -- there are other
examples of the current form, such as ibm,#dma-address-cells and ti,#tlb-
entries, and the current form makes more logical sense (# is part of the
property name, not the vendor). Oh well.
> Required properites:
> - reg : Offset and length of the register set of the RCPM block.
> - - fsl,#rcpm-wakeup-cells : The number of IPPDEXPCR register cells in the
> + - #fsl,rcpm-wakeup-cells : The number of IPPDEXPCR register cells in the
> fsl,rcpm-wakeup property.
> - compatible : Must contain a chip-specific RCPM block compatible string
> and (if applicable) may contain a chassis-version RCPM compatible
> @@ -20,6 +20,7 @@ Required properites:
> * "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
> + * "fsl,qoriq-rcpm-2.1+": for chassis 2.1+ rcpm
Is there something actually called "2.1+"? It looks a bit like an attempt to
claim compatibility with all future versions. If the former, is it a name
that comes from the hardware side with an intent for it to describe a stable
interface, or are we later going to see a patch changing some by-then-existing
device trees from "2.1+" to "2.1++" when some new incompatibility is found?
Perhaps it would be better to bind to the specific chip compatibles.
-Scott
next prev parent reply other threads:[~2019-10-24 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 3:49 [PATCH v7 1/3] PM: wakeup: Add routine to help fetch wakeup source object Ran Wang
2019-10-21 3:49 ` [PATCH v7 2/3] Documentation: dt: binding: fsl: Add 'little-endian' and update Chassis define Ran Wang
2019-10-24 18:33 ` Scott Wood [this message]
2019-10-25 2:40 ` Ran Wang
2019-10-21 3:49 ` [PATCH v7 3/3] soc: fsl: add RCPM driver Ran Wang
2019-10-24 2:57 ` kbuild test robot
2019-10-21 8:38 ` [PATCH v7 1/3] PM: wakeup: Add routine to help fetch wakeup source object Rafael J. Wysocki
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=ef150e9eb155eff410194ba5362ef404ce117c4a.camel@buserror.net \
--to=oss@buserror.net \
--cc=biwen.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=ran.wang_1@nxp.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.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).