[PATCH v3 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation
Jayachandran C
jnair at caviumnetworks.com
Tue Feb 7 21:32:35 PST 2017
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 at 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 at 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.
More information about the linux-arm-kernel
mailing list