From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 1/3] arm64: add THUNDER2 processor family
Date: Mon, 6 Feb 2017 10:06:08 +0000 [thread overview]
Message-ID: <20170206100608.GA8540@arm.com> (raw)
In-Reply-To: <1486233461-2679-2-git-send-email-jnair@caviumnetworks.com>
On Sat, Feb 04, 2017 at 06:37:39PM +0000, Jayachandran C wrote:
> Add support for ThunderX2 CN99XX arm64 server processors.
>
> Introduce a new arm64 platform config option ARCH_THUNDER2 for these
> processors. Add device tree files boot/dts/cavium/thunder-99xx.dtsi for
> on-chip devices and boot/dts/cavium/thunder-99xx.dts for the evaluation
> board.
>
> Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
> ---
> arch/arm64/Kconfig.platforms | 7 ++
> arch/arm64/boot/dts/cavium/Makefile | 1 +
> arch/arm64/boot/dts/cavium/thunder-99xx.dts | 34 +++++++
> arch/arm64/boot/dts/cavium/thunder-99xx.dtsi | 147 +++++++++++++++++++++++++++
This is basically identical to vulcan.dtsi. Do we really need both in the
tree?
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Jayachandran C <jnair-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH RESEND 1/3] arm64: add THUNDER2 processor family
Date: Mon, 6 Feb 2017 10:06:08 +0000 [thread overview]
Message-ID: <20170206100608.GA8540@arm.com> (raw)
In-Reply-To: <1486233461-2679-2-git-send-email-jnair-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
On Sat, Feb 04, 2017 at 06:37:39PM +0000, Jayachandran C wrote:
> Add support for ThunderX2 CN99XX arm64 server processors.
>
> Introduce a new arm64 platform config option ARCH_THUNDER2 for these
> processors. Add device tree files boot/dts/cavium/thunder-99xx.dtsi for
> on-chip devices and boot/dts/cavium/thunder-99xx.dts for the evaluation
> board.
>
> Signed-off-by: Jayachandran C <jnair-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
> ---
> arch/arm64/Kconfig.platforms | 7 ++
> arch/arm64/boot/dts/cavium/Makefile | 1 +
> arch/arm64/boot/dts/cavium/thunder-99xx.dts | 34 +++++++
> arch/arm64/boot/dts/cavium/thunder-99xx.dtsi | 147 +++++++++++++++++++++++++++
This is basically identical to vulcan.dtsi. Do we really need both in the
tree?
Will
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-06 10:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 18:37 [PATCH RESEND 0/3] arm64: Add ARCH_THUNDER2 Jayachandran C
2017-02-04 18:37 ` Jayachandran C
2017-02-04 18:37 ` [PATCH RESEND 1/3] arm64: add THUNDER2 processor family Jayachandran C
2017-02-04 18:37 ` Jayachandran C
2017-02-06 10:06 ` Will Deacon [this message]
2017-02-06 10:06 ` Will Deacon
2017-02-06 13:44 ` Arnd Bergmann
2017-02-06 13:44 ` Arnd Bergmann
2017-02-06 15:21 ` Jayachandran C
2017-02-06 15:21 ` Jayachandran C
2017-02-06 15:38 ` Arnd Bergmann
2017-02-06 15:38 ` Arnd Bergmann
2017-02-07 9:41 ` Jayachandran C
2017-02-07 9:41 ` Jayachandran C
2017-02-04 18:37 ` [PATCH RESEND 2/3] dt-bindings: arm64 ARCH_THUNDER2 platform documentation Jayachandran C
2017-02-04 18:37 ` Jayachandran C
2017-02-04 18:37 ` [PATCH RESEND 3/3] arm64: add ARCH_THUNDER2 to defconfig Jayachandran C
2017-02-04 18:37 ` 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=20170206100608.GA8540@arm.com \
--to=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.