From: jnair@caviumnetworks.com (Jayachandran C)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation
Date: Wed, 8 Feb 2017 05:32:35 +0000	[thread overview]
Message-ID: <20170208053234.GA3102@localhost> (raw)
In-Reply-To: <CAL_Jsq+i2evzVnQKf3qYMYJVZ=ecdSQObGy8CMn7aMoxBi_PTg@mail.gmail.com>
On Tue, Feb 07, 2017 at 04:35:24PM -0600, Rob Herring wrote:
> On Tue, Feb 7, 2017 at 3:19 PM, Jayachandran C <jnair@caviumnetworks.com> wrote:
> > Add documentation for Cavium ThunderX2 CN99XX ARM64 processor family.
> > The the SoC will use the ID "cavium,thunder-99xx".
> >
> > Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
> > ---
> >
> > All marketing material refers to the chip as CN99XX (like CN88XX before)
> > that is why I have used the wildcard-like 99xx here.
> >
> >  Documentation/devicetree/bindings/arm/cavium-thunder2.txt | 5 +++++
> >  1 file changed, 5 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/arm/cavium-thunder2.txt
> >
> > diff --git a/Documentation/devicetree/bindings/arm/cavium-thunder2.txt b/Documentation/devicetree/bindings/arm/cavium-thunder2.txt
> > new file mode 100644
> > index 0000000..82276a2
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/cavium-thunder2.txt
> > @@ -0,0 +1,5 @@
> > +Cavium Thunder2 Family device tree bindings
> > +-------------------------------------------
> > +
> > +Boards with Cavium ThunderX2 CN99XX shall have the root property:
> > +  compatible = "cavium,thunder-99xx";
> 
> Is it ThunderX2 or Thunder2? What happened to "CN" in the compatible
> string. There's a lot of inconsistencies here.
I have followed the exiting Thunder naming as well as general DT
conventions, Basically:
Platform - ARCH_THUNDER2  (for ThunderX2 CN99XX, ARCH_THUNDER is
           for ThunderX CN8?XX)
Core - cavium,thunder2 (ThunderX2 cpu core, "cavium,thunder" is ThunderX core)
Board/SoC - cavium,thunder-99xx (for ThunderX2, "cavium,thunder-88xx"
          is existing ThunderX board)
Thunder2 because it is based on the next generation Thunder core, and
processor family is ThunderX2 CN99XX.
I had thought thru other possibilities as well, this seems the best I
could come up with.
JC.
next prev parent reply	other threads:[~2017-02-08  5:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 21:19 [PATCH v3 0/5] Add Cavium ARCH_THUNDER2 platform Jayachandran C
2017-02-07 21:19 ` [PATCH v3 1/5] arm64: add THUNDER2 processor family Jayachandran C
2017-02-07 21:19 ` [PATCH v3 2/5] MAINTAINERS: Add Cavium ThunderX2 entry Jayachandran C
2017-02-07 21:19 ` [PATCH v3 3/5] arm64: dts: add device tree for ARCH_THUNDER2 Jayachandran C
2017-02-07 21:19 ` [PATCH v3 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation Jayachandran C
2017-02-07 22:35   ` Rob Herring
2017-02-08  5:32     ` Jayachandran C [this message]
2017-02-08  8:42       ` Arnd Bergmann
2017-02-09 19:05         ` Jayachandran C
2017-02-09 19:12         ` [PATCH v4 3/5] arm64: dts: add device tree for ARCH_THUNDER2 Jayachandran C
2017-02-09 19:13         ` [PATCH v4 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation Jayachandran C
2017-02-10 14:55           ` Rob Herring
2017-02-10 15:07             ` Jayachandran C
2017-02-10 17:32               ` Rob Herring
2017-02-11 16:05                 ` Jayachandran C
2017-02-07 21:19 ` [PATCH v3 5/5] arm64: add ARCH_THUNDER2 to defconfig Jayachandran C
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=20170208053234.GA3102@localhost \
    --to=jnair@caviumnetworks.com \
    --cc=linux-arm-kernel@lists.infradead.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).