mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: Russell King <linux@armlinux.org.uk>,
	Phil Elwell <phil@raspberrypi.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Stefan Wahren <wahrenst@gmx.net>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"moderated list:BROADCOM BCM2835 ARM ARCHITECTURE" 
	<linux-rpi-kernel@lists.infradead.org>
Subject: Re: [RFC] ARM: add multi_v7_lpae_defconfig
Date: Wed, 12 Feb 2020 12:27:02 -0800	[thread overview]
Message-ID: <e061bc24-9832-cfb1-ab64-1cf164fe599e@gmail.com> (raw)
In-Reply-To: <CAK8P3a1tLrkymeJfXvDk_kxPvW_PQy6zNmrmO++dOPCWm71vOA@mail.gmail.com>

On 2/12/20 12:19 PM, Arnd Bergmann wrote:
> On Fri, Jan 10, 2020 at 6:35 PM Nicolas Saenz Julienne
> <nsaenzjulienne@suse.de> wrote:
>>
>> The only missing configuration option preventing us from using
>> multi_v7_defconfig with the RPi4 is ARM_LPAE. It's needed as the PCIe
>> controller found on the SoC depends on 64bit addressing, yet can't be
>> included as not all v7 boards support LPAE.
>>
>> Introduce multi_v7_lpae_defconfig, built off multi_v7_defconfig, which will
>> avoid us having to duplicate and maintain multiple similar configurations.
>>
>> Note that merge_into_defconfig was taken from arch/powerpc/Makefile.
>>
>> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> 
> I like the idea, but I would note that a lot of platforms enabled in
> multi_v7_defconfig do not support LPAE. In particular, the first ARMv7
> cores (Cortex-A8, -A9, -A5, and PJ4) don't, but the later ones (Cortex-A7,
> -A15, -A17, and PJ4C-MP) do.
> 
> Here is a list from the defconfig file
> 

[snip]

> CONFIG_ARCH_BCM=y
> CONFIG_ARCH_BCM_CYGNUS=y
> CONFIG_ARCH_BCM_HR2=y
> CONFIG_ARCH_BCM_NSP=y
> CONFIG_ARCH_BCM_5301X=y
> CONFIG_ARCH_BCM_281XX=y
> CONFIG_ARCH_BCM_21664=y
> CONFIG_ARCH_BCM_63XX=y
> CONFIG_ARCH_BRCMSTB=y
> 
> I think most of the above are A9, but not sure

63138 is Cortex-A9, 63148 and BRCMSTB are using a Brahma-B15 CPU which
is LPAE capable. 23550 is A7 and every others are Cortex-A9.
-- 
Florian

      reply	other threads:[~2020-02-12 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 17:34 Nicolas Saenz Julienne
2020-01-10 17:56 ` Florian Fainelli
2020-02-12 20:19 ` Arnd Bergmann
2020-02-12 20:27   ` Florian Fainelli [this message]

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=e061bc24-9832-cfb1-ab64-1cf164fe599e@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=nsaenzjulienne@suse.de \
    --cc=phil@raspberrypi.org \
    --cc=wahrenst@gmx.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®