[PATCH v3 0/5] Add Cavium ARCH_THUNDER2 platform

[PATCH v3 0/5] Add Cavium ARCH_THUNDER2 platform

[Jayachandran C]

Here's another revision of the patchset, updated based on the last
discussion.

This patchset adds support for the new ThunderX2 CN99XX processor
family.

Changes are to add: the config option, the required device tree files,
the device tree bindings documentation and the defconfig entry.

Changes from v2 -> v3:
* drop thunder-99xx.dtsi which was a copy of vulcan.dtsi, include file
  instead
* Don't add cavium,thunder2 processor compat ID, not needed until vulcan.dtsi
  moves to dts/cavium/
* select ARCH_VULCAN when ARCH_THUNDER2 is selected (for now)
* dropped Ack from Rob H due to change in specific patch

Changes from v1 -> v2:
* split Kconfig.platforms changes and device tree changes
* Added MAINTAINERS entry

JC.

Jayachandran C (5):
  arm64: add THUNDER2 processor family
  MAINTAINERS: Add Cavium ThunderX2 entry
  arm64: dts: add device tree for ARCH_THUNDER2
  dt-bindings: arm64 ARCH_THUNDER2 platform documentation
  arm64: add ARCH_THUNDER2 to defconfig

 .../devicetree/bindings/arm/cavium-thunder2.txt    |  5 ++++
 MAINTAINERS                                        |  7 +++++
 arch/arm64/Kconfig.platforms                       |  8 +++++
 arch/arm64/boot/dts/cavium/Makefile                |  1 +
 arch/arm64/boot/dts/cavium/thunder-99xx.dts        | 34 ++++++++++++++++++++++
 arch/arm64/configs/defconfig                       |  1 +
 6 files changed, 56 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/cavium-thunder2.txt
 create mode 100644 arch/arm64/boot/dts/cavium/thunder-99xx.dts

-- 
2.7.4

[PATCH v3 1/5] arm64: add THUNDER2 processor family

[Jayachandran C]

Add support for ThunderX2 CN99XX arm64 server processors. Introduce a
new arm64 platform config option ARCH_THUNDER2 for these processors.

ARCH_THUNDER2 has the same on-chip devices as ARCH_VULCAN, so select
ARCH_VULCAN for now, until the driver dependencies are updated.

Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
---
 arch/arm64/Kconfig.platforms | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index 715ef12..1ee377d 100644
--- a/arch/arm64/Kconfig.platforms
+++ b/arch/arm64/Kconfig.platforms
@@ -190,6 +190,14 @@ config ARCH_THUNDER
 	help
 	  This enables support for Cavium's Thunder Family of SoCs.
 
+config ARCH_THUNDER2
+	bool "Cavium ThunderX2 Server Processors"
+	select ARCH_VULCAN
+	select GPIOLIB
+	help
+	  This enables support for Cavium's ThunderX2 CN99XX family of
+	  server processors.
+
 config ARCH_UNIPHIER
 	bool "Socionext UniPhier SoC Family"
 	select ARCH_HAS_RESET_CONTROLLER
-- 
2.7.4

[PATCH v3 2/5] MAINTAINERS: Add Cavium ThunderX2 entry

[Jayachandran C]

Add maintainer information for Cavium ThunderX2 ARM64 processor
family.

Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
---
 MAINTAINERS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 187b961..4f788ad 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2972,6 +2972,13 @@ S:	Maintained
 F:	drivers/iio/light/cm*
 F:	Documentation/devicetree/bindings/i2c/trivial-admin-guide/devices.rst
 
+CAVIUM THUNDERX2 ARM64 SOC
+M:	Jayachandran C <jnair@caviumnetworks.com>
+L:	linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
+S:	Maintained
+F:	arch/arm64/boot/dts/cavium/thunder-99xx*
+F:	Documentation/devicetree/bindings/arm/cavium-thunder2.txt
+
 CAVIUM I2C DRIVER
 M:	Jan Glauber <jglauber@cavium.com>
 M:	David Daney <david.daney@cavium.com>
-- 
2.7.4

[PATCH v3 3/5] arm64: dts: add device tree for ARCH_THUNDER2

[Jayachandran C]

Add board device tree file for Cavium's ThunderX2 CN99XX arm64
server processors. The SoC is compatible with the discontinued
Broadcom Vulcan ARM64 SoC.

Update the Makefile to build the thunder-99xx.dtb when the
ARCH_THUNDER2 option is selected.

Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
---
 arch/arm64/boot/dts/cavium/Makefile         |  1 +
 arch/arm64/boot/dts/cavium/thunder-99xx.dts | 34 +++++++++++++++++++++++++++++
 2 files changed, 35 insertions(+)
 create mode 100644 arch/arm64/boot/dts/cavium/thunder-99xx.dts

diff --git a/arch/arm64/boot/dts/cavium/Makefile b/arch/arm64/boot/dts/cavium/Makefile
index e34f89d..557c8be 100644
--- a/arch/arm64/boot/dts/cavium/Makefile
+++ b/arch/arm64/boot/dts/cavium/Makefile
@@ -1,4 +1,5 @@
 dtb-$(CONFIG_ARCH_THUNDER) += thunder-88xx.dtb
+dtb-$(CONFIG_ARCH_THUNDER2) += thunder-99xx.dtb
 
 always		:= $(dtb-y)
 subdir-y	:= $(dts-dirs)
diff --git a/arch/arm64/boot/dts/cavium/thunder-99xx.dts b/arch/arm64/boot/dts/cavium/thunder-99xx.dts
new file mode 100644
index 0000000..39614b8
--- /dev/null
+++ b/arch/arm64/boot/dts/cavium/thunder-99xx.dts
@@ -0,0 +1,34 @@
+/*
+ * dts file for Cavium ThunderX2 CN99XX based Evaluation Boards
+ *
+ * Copyright (c) 2017 Cavium Inc.
+ * Copyright (c) 2013-2016 Broadcom
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of
+ * the License, or (at your option) any later version.
+ */
+
+/dts-v1/;
+
+#include "../broadcom/vulcan.dtsi"
+
+/ {
+	model = "Cavium ThunderX2 CN99XX";
+	compatible = "cavium,thunder-99xx", "brcm,vulcan-soc";
+
+	memory {
+		device_type = "memory";
+		reg = <0x00000000 0x80000000 0x0 0x80000000>,  /* 2G @ 2G  */
+		      <0x00000008 0x80000000 0x0 0x80000000>;  /* 2G @ 34G */
+	};
+
+	aliases {
+		serial0 = &uart0;
+	};
+
+	chosen {
+		stdout-path = "serial0:115200n8";
+	};
+};
-- 
2.7.4

[PATCH v3 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Jayachandran C]

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";
-- 
2.7.4

[PATCH v3 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Rob Herring]

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.

Rob

[PATCH v3 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Jayachandran C]

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.

[PATCH v3 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Arnd Bergmann]

On Wed, Feb 8, 2017 at 6:32 AM, Jayachandran C <jnair@caviumnetworks.com> wrote:
> 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:
>> > 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)

The platform name is fine, we don't care too much about that as it is
easily changed
if necessary.

> 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.

We should really avoid having the 'xx' placeholder in there but instead put
actual chip names in the compatible string, preferably the real ID such as
"cn8890" for the older chip. I see that we got it wrong for thunder-88xx.dts,
but that is no reason to duplicate the mistake.

     Arnd

[PATCH v3 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Jayachandran C]

On Wed, Feb 08, 2017 at 09:42:38AM +0100, Arnd Bergmann wrote:
> On Wed, Feb 8, 2017 at 6:32 AM, Jayachandran C <jnair@caviumnetworks.com> wrote:
> > 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:
> >> > 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)
> 
> The platform name is fine, we don't care too much about that as it is
> easily changed
> if necessary.
> 
> > 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.
> 
> We should really avoid having the 'xx' placeholder in there but instead put
> actual chip names in the compatible string, preferably the real ID such as
> "cn8890" for the older chip. I see that we got it wrong for thunder-88xx.dts,
> but that is no reason to duplicate the mistake.

Ok. Looks like 1,2,5 of the patchset is already applied. Thanks!

I will follow up with v4 of 3,4 with a better ID.

JC.

[PATCH v4 3/5] arm64: dts: add device tree for ARCH_THUNDER2

[Jayachandran C]

Add a device tree file for boards using the Cavium's ThunderX2 CN99XX
ARM64 processors. The SoC is compatible with the discontinued Broadcom
Vulcan ARM64 SoC.

Update the Makefile to build the thunder-99xx.dtb when ARCH_THUNDER2
option is selected.

Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
---

Patches 1,2,5 of this series have been applied, sending this with
suggested changes to compat string.

v3->v4
 * compat ID updated to follow convention.

 arch/arm64/boot/dts/cavium/Makefile         |  1 +
 arch/arm64/boot/dts/cavium/thunder-99xx.dts | 34 +++++++++++++++++++++++++++++
 2 files changed, 35 insertions(+)
 create mode 100644 arch/arm64/boot/dts/cavium/thunder-99xx.dts

diff --git a/arch/arm64/boot/dts/cavium/Makefile b/arch/arm64/boot/dts/cavium/Makefile
index e34f89d..557c8be 100644
--- a/arch/arm64/boot/dts/cavium/Makefile
+++ b/arch/arm64/boot/dts/cavium/Makefile
@@ -1,4 +1,5 @@
 dtb-$(CONFIG_ARCH_THUNDER) += thunder-88xx.dtb
+dtb-$(CONFIG_ARCH_THUNDER2) += thunder-99xx.dtb
 
 always		:= $(dtb-y)
 subdir-y	:= $(dts-dirs)
diff --git a/arch/arm64/boot/dts/cavium/thunder-99xx.dts b/arch/arm64/boot/dts/cavium/thunder-99xx.dts
new file mode 100644
index 0000000..6d6e8af
--- /dev/null
+++ b/arch/arm64/boot/dts/cavium/thunder-99xx.dts
@@ -0,0 +1,34 @@
+/*
+ * dts file for Cavium ThunderX2 CN99XX based Evaluation Boards
+ *
+ * Copyright (c) 2017 Cavium Inc.
+ * Copyright (c) 2013-2016 Broadcom
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of
+ * the License, or (at your option) any later version.
+ */
+
+/dts-v1/;
+
+#include "../broadcom/vulcan.dtsi"
+
+/ {
+	model = "Cavium ThunderX2 CN99XX";
+	compatible = "cavium,thunderx2-cn9900", "brcm,vulcan-soc";
+
+	memory {
+		device_type = "memory";
+		reg = <0x00000000 0x80000000 0x0 0x80000000>,  /* 2G @ 2G  */
+		      <0x00000008 0x80000000 0x0 0x80000000>;  /* 2G @ 34G */
+	};
+
+	aliases {
+		serial0 = &uart0;
+	};
+
+	chosen {
+		stdout-path = "serial0:115200n8";
+	};
+};
-- 
2.7.4

[PATCH v4 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Jayachandran C]

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"
 			    "faraday,fa526"
 			    "intel,sa110"
 			    "intel,sa1100"
-- 
2.7.4

[PATCH v4 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Rob Herring]

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?

>                             "faraday,fa526"
>                             "intel,sa110"
>                             "intel,sa1100"
> --
> 2.7.4
>

[PATCH v4 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Jayachandran C]

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.

[PATCH v4 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Rob Herring]

On Fri, Feb 10, 2017 at 9:07 AM, Jayachandran C
<jnair@caviumnetworks.com> wrote:
> 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.

Okay, new ID registers is good enough reason. I'd just let brcm,vulcan
die though I have no idea how many Broadcom systems there are out in
the wild (and ones that you care about DT on).

Acked-by: Rob Herring <robh@kernel.org>

Rob

[PATCH v4 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation

[Jayachandran C]

On Fri, Feb 10, 2017 at 11:32:29AM -0600, Rob Herring wrote:
> On Fri, Feb 10, 2017 at 9:07 AM, Jayachandran C
> <jnair@caviumnetworks.com> wrote:
> > 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.
> 
> Okay, new ID registers is good enough reason. I'd just let brcm,vulcan
> die though I have no idea how many Broadcom systems there are out in
> the wild (and ones that you care about DT on).

This is not an issue. Broadcom did not take the chip into production, and
the eval systems are at the new habitat :)
 
> Acked-by: Rob Herring <robh@kernel.org>

Thanks,
JC.

[PATCH v3 5/5] arm64: add ARCH_THUNDER2 to defconfig

[Jayachandran C]

This will allow the default kernel build to boot on Cavium ThunderX2
CN99XX processors.

Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
---
 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 33b744d..7a9c262 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -53,6 +53,7 @@ CONFIG_ARCH_STRATIX10=y
 CONFIG_ARCH_TEGRA=y
 CONFIG_ARCH_SPRD=y
 CONFIG_ARCH_THUNDER=y
+CONFIG_ARCH_THUNDER2=y
 CONFIG_ARCH_UNIPHIER=y
 CONFIG_ARCH_VEXPRESS=y
 CONFIG_ARCH_VULCAN=y
-- 
2.7.4