[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150721145643.GD10595@leverpostej>
Date: Tue, 21 Jul 2015 15:56:43 +0100
From: Mark Rutland <mark.rutland@....com>
To: Jisheng Zhang <jszhang@...vell.com>
Cc: Catalin Marinas <Catalin.Marinas@....com>,
Will Deacon <Will.Deacon@....com>,
"khilman@...aro.org" <khilman@...aro.org>,
"arnd@...db.de" <arnd@...db.de>, "olof@...om.net" <olof@...om.net>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"galak@...eaurora.org" <galak@...eaurora.org>,
Pawel Moll <Pawel.Moll@....com>,
Marc Zyngier <Marc.Zyngier@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: Add dts files for Marvell Berlin4CT SoC
On Tue, Jul 21, 2015 at 03:50:06PM +0100, Jisheng Zhang wrote:
> Dear Mark,
>
> Thanks a lot for so quick review!
>
> On Tue, 21 Jul 2015 15:34:26 +0100
> Mark Rutland <mark.rutland@....com> wrote:
>
> > Hi,
> >
> > > +/dts-v1/;
> > > +
> > > +/memreserve/ 0x00000000 0x01000000;
> >
> > What's this reservation for?
>
> This is reserved for some firmwares' usage.
>
> >
> > Given you're using PSCI I can't see why we'd expect the kernel to map
> > but not use some memory.
>
> Is it acceptable that we make memory start at 0x01000000 instead of reservation?
Yes, though it would still be worth a comment as to why that memory
can't be used.
Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists