linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jnair@caviumnetworks.com (Jayachandran C)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation
Date: Fri, 10 Feb 2017 15:07:54 +0000	[thread overview]
Message-ID: <20170210150754.GA1874@localhost> (raw)
In-Reply-To: <CAL_JsqKm-c6D_fki_TsRYKH3aGoC5GE7n0DazNi7P268aj-93g@mail.gmail.com>

On Fri, Feb 10, 2017 at 08:55:31AM -0600, Rob Herring wrote:
> On Thu, Feb 9, 2017 at 1:13 PM, Jayachandran C <jnair@caviumnetworks.com> wrote:
> > Add documentation for Cavium ThunderX2 CN99XX ARM64 processor family.
> > The the SoC will use the ID "cavium,thunderx2-cn9900".
> >
> > Add documentation entry for the "cavium,thunder2" cpu core as well.
> >
> > Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
> > ---
> >
> > v3->v4
> > Documentation updates to reflect changes in device tree.
> >
> >  Documentation/devicetree/bindings/arm/cavium-thunder2.txt | 8 ++++++++
> >  Documentation/devicetree/bindings/arm/cpus.txt            | 1 +
> >  2 files changed, 9 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..dc5dd65
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/cavium-thunder2.txt
> > @@ -0,0 +1,8 @@
> > +Cavium ThunderX2 CN99XX platform tree bindings
> > +----------------------------------------------
> > +
> > +Boards with Cavium ThunderX2 CN99XX SoC shall have the root property:
> > +  compatible = "cavium,thunderx2-cn9900", "brcm,vulcan-soc";
> > +
> > +These SoC uses the "cavium,thunder2" core which will be compatible
> > +with "brcm,vulcan".
> > diff --git a/Documentation/devicetree/bindings/arm/cpus.txt b/Documentation/devicetree/bindings/arm/cpus.txt
> > index a1bcfee..74f0b23 100644
> > --- a/Documentation/devicetree/bindings/arm/cpus.txt
> > +++ b/Documentation/devicetree/bindings/arm/cpus.txt
> > @@ -169,6 +169,7 @@ nodes to be present and contain the properties described below.
> >                             "brcm,brahma-b15"
> >                             "brcm,vulcan"
> >                             "cavium,thunder"
> > +                           "cavium,thunder2"
> 
> Is this the same as brcm,vulcan?

It will have a different CPU ID, with different implementer and part num,
but compatible with "brcm,vulcan". In the ThunderX2 dtsi file (once
ARCH_VULCAN goes away), we want to be compatable = "cavium,thunder2", with
maybe "brcm,vulcan" after that.

JC.

  reply	other threads:[~2017-02-10 15:07 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
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 [this message]
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=20170210150754.GA1874@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).