From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
Jason Cooper <jason@lakedaemon.net>,
devicetree@vger.kernel.org,
Antoine Tenart <antoine.tenart@bootlin.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Gregory Clement <gregory.clement@bootlin.com>,
Will Deacon <will.deacon@arm.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Nadav Haklai <nadavh@marvell.com>,
Rob Herring <robh+dt@kernel.org>, Victor Gu <xigu@marvell.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH] arm64: dts: marvell: armada-37xx: reserve memory for ATF
Date: Mon, 23 Apr 2018 10:31:27 +0200 [thread overview]
Message-ID: <20180423103127.5b9ac041@xps13> (raw)
In-Reply-To: <20180421161859.22d1ed18@windsurf>
Hi Thomas,
On Sat, 21 Apr 2018 16:18:59 +0200, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> On Sat, 21 Apr 2018 16:03:42 +0200, Miquel Raynal wrote:
> > From: Victor Gu <xigu@marvell.com>
> >
> > The PSCI area should be reserved in Linux for PSCI operations such as
> > suspend/resume.
> >
> > Reserve 2MiB of memory which matches the area used by ATF (BL1, BL2,
> > BL3x, see [1] in ATF source code). This covers all PSCI code and data
> > area and is 2MiB aligned, which is required by Linux for huge pages
> > handling.
> >
> > [1] plat/marvell/a3700/common/include/platform_def.h
> >
> > Signed-off-by: Victor Gu <xigu@marvell.com>
> > [miquel.raynal@bootlin.com: reword of commit message]
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> Shouldn't this be done automatically by the bootloader, before passing
> the DTB to the kernel ?
I am working with a 2017.09 mainline U-Boot.
I did not know the bootloader was supposedly in charge of that. But
what if it fails doing it? Fixing the bootloader is one thing, I assume
very few people would update it. Is it worth keeping this in Linux DT?
Thanks,
Miquèl
--
Miquel Raynal, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-04-23 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 14:03 [PATCH] arm64: dts: marvell: armada-37xx: reserve memory for ATF Miquel Raynal
2018-04-21 14:18 ` Thomas Petazzoni
2018-04-23 8:31 ` Miquel Raynal [this message]
2018-04-23 12:49 ` Thomas Petazzoni
2018-04-23 15:15 ` Miquel Raynal
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=20180423103127.5b9ac041@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maxime.chevallier@bootlin.com \
--cc=nadavh@marvell.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=will.deacon@arm.com \
--cc=xigu@marvell.com \
/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).