linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@nxp.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Shawn Guo <shawnguo@kernel.org>,
	DTML <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH] ARM: dts: Makefile: build arm64 device tree
Date: Tue, 17 Mar 2020 01:44:30 +0000	[thread overview]
Message-ID: <AM0PR04MB44812054118E892BEFFACD7F88F60@AM0PR04MB4481.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM0PR04MB4481CD81915F8A9FB115A97788FA0@AM0PR04MB4481.eurprd04.prod.outlook.com>

Hi Arnd,

> Subject: RE: [PATCH] ARM: dts: Makefile: build arm64 device tree
> 
> Hi Arnd,
> 
> > Subject: Re: [PATCH] ARM: dts: Makefile: build arm64 device tree
> >
> > On Fri, Mar 13, 2020 at 4:38 AM <peng.fan@nxp.com> wrote:
> > >
> > > From: Peng Fan <peng.fan@nxp.com>
> > >
> > > To support aarch32 mode linux on aarch64 hardware, we need build the
> > > device tree, so include the arm64 device tree path.
> > >
> > > Signed-off-by: Peng Fan <peng.fan@nxp.com>
> > > ---
> >
> > There are a few other platforms with similar requirements, in
> > particular bcm2837, so maybe try doing it the same way they do, see
> > arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts
> >
> > > V1:
> > >  This is just the device tree part. Besides this,  I am not sure
> > > whether need to create a standalone defconfig under arm32  for
> > > aarch32 mode linux on aarch64 hardware, or use multi_v7_defconfig.
> > >  multi_v7_defconfig should be ok, need to include LPAE config.
> >
> > I'd rather not have a standalone defconfig for it, given that we have
> > a single defconfig for all armv6/armv7/armv7hf i.mx machines.
> >
> > There was a suggestion to use a fragment for enabling an LPAE
> > multi_v7_defconfig recently, which I think is still under discussion
> > but should also help here, both with imx_v6_v7_defconfig and
> multi_v7_defconfig.
> >
> > Can you remind us why this platform needs LPAE? Is it only needed to
> > support more than 4GB of RAM, or something else on top of that?
> 
> Currently I only tested LPAE enabled arm32 kernel, I'll give a try with LPAE
> disabled later.

Tested with imx_v6_v7_defconfig without LPAE, smp boots up with nfsroot.

Thanks,
Peng.

> 
> Thanks,
> Peng.
> > Note that users that actually have 4GB or more on i.mx8 should really
> > run a 64-bit kernel anyway, even if they prefer using 32-bit user space.
> >
> > Turning on LPAE not only disables imx3 and imx5 but also the Cortex-A9
> > based
> > imx6 variants.
> >
> >       Arnd

      reply	other threads:[~2020-03-17  1:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13  3:31 [PATCH] ARM: dts: Makefile: build arm64 device tree peng.fan
2020-03-13 10:23 ` Arnd Bergmann
2020-03-13 10:47   ` Masahiro Yamada
2020-03-13 12:39   ` Peng Fan
2020-03-17  1:44     ` Peng Fan [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=AM0PR04MB44812054118E892BEFFACD7F88F60@AM0PR04MB4481.eurprd04.prod.outlook.com \
    --to=peng.fan@nxp.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).