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

On Fri, Feb 10, 2017 at 9:07 AM, Jayachandran C
[off-list ref] wrote:

On Fri, Feb 10, 2017 at 08:55:31AM -0600, Rob Herring wrote:

quoted

On Thu, Feb 9, 2017 at 1:13 PM, Jayachandran C [off-list ref] wrote:

quoted

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

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