[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4284367.sAeqrVzAbo@wuerfel>
Date: Wed, 03 Feb 2016 10:11:18 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Gregory CLEMENT <gregory.clement@...e-electrons.com>
Cc: Jisheng Zhang <jszhang@...vell.com>,
Jason Cooper <jason@...edaemon.net>,
Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
arm@...nel.org, Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Jonathan Corbet <corbet@....net>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, linux-ide@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, Hans de Goede <hdegoede@...hat.com>,
linux-serial@...r.kernel.org, Jiri Slaby <jslaby@...e.com>,
Tejun Heo <tj@...nel.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 03/10] arm64: add Armada 3700 architecture entry
On Wednesday 03 February 2016 08:55:22 Gregory CLEMENT wrote:
> >>
> >> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> >> index 21074f674bde..7da341f7b90d 100644
> >> --- a/arch/arm64/Kconfig.platforms
> >> +++ b/arch/arm64/Kconfig.platforms
> >> @@ -1,5 +1,11 @@
> >> menu "Platform selection"
> >>
> >> +config ARCH_ARMADA_3700
> >
> > Would it be better to use ARCH_MVEBU? IMHO, there will be more ARMv8 SoCs
> > from our EBU, do we plan to add one CONFIG_ARMADA_yyzz for each SoC?
>
> Not for each SoC but for each family, yes. As we did for the other mvebu
> SoC families.
>
We tend to use a little more general config strings for arm64 than we have
for arm32. I think just using ARCH_MVEBU is fine here, no need to list
the 3700 series separately.
Arnd
Powered by blists - more mailing lists