[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJapPM6CpaG+AYDAUQajZ4V5jREdCwA5F4vkD5jqC3bzg@mail.gmail.com>
Date: Fri, 9 Oct 2015 08:17:16 -0500
From: Rob Herring <robherring2@...il.com>
To: Leo Yan <leo.yan@...aro.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Bintian Wang <bintian.wang@...wei.com>,
Haojian Zhuang <haojian.zhuang@...aro.org>,
Wei Xu <xuwei5@...ilicon.com>,
Yiping Xu <xuyiping@...ilicon.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Brown <broonie@...nel.org>,
Tyler Baker <tyler.baker@...aro.org>
Subject: Re: [PATCH 1/4] arm64: dts: Reserve memory regions for hi6220
On Thu, Oct 8, 2015 at 11:36 PM, Leo Yan <leo.yan@...aro.org> wrote:
> On Hi6220, below memory regions in DDR have specific purpose:
>
> 0x05e0,0000 - 0x05ef,ffff: For MCU firmware using at runtime;
> 0x06df,f000 - 0x06df,ffff: For mailbox message data;
> 0x0740,f000 - 0x0740,ffff: For MCU firmware's section;
> 0x3e00,0000 - 0x3fff,ffff: For OP-TEE.
>
> This patch reserves these memory regions in DT.
>
> Signed-off-by: Leo Yan <leo.yan@...aro.org>
> ---
> arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> index e36a539..e3f4cb3 100644
> --- a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> +++ b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> @@ -7,9 +7,6 @@
>
> /dts-v1/;
>
> -/*Reserved 1MB memory for MCU*/
> -/memreserve/ 0x05e00000 0x00100000;
> -
Why does memreserve not work for you? You can have multiple entries.
> #include "hi6220.dtsi"
>
> / {
> @@ -24,8 +21,19 @@
> stdout-path = "serial0:115200n8";
> };
>
> + /*
> + * Reserve below regions from memory node:
> + *
> + * - 0x05e0,0000 - 0x05ef,ffff: MCU firmware runtime using
> + * - 0x06df,f000 - 0x06df,ffff: Mailbox message data
> + * - 0x0740,f000 - 0x0740,ffff: MCU firmware section
> + * - 0x3e00,0000 - 0x3fff,ffff: OP-TEE
> + */
> memory@0 {
> device_type = "memory";
> - reg = <0x0 0x0 0x0 0x40000000>;
> + reg = <0x00000000 0x00000000 0x00000000 0x05e00000>,
> + <0x00000000 0x05f00000 0x00000000 0x00eff000>,
> + <0x00000000 0x06e00000 0x00000000 0x0060f000>,
> + <0x00000000 0x07410000 0x00000000 0x36bf0000>;
No, don't do this. Please use memreserve or reserved-memory binding[1]
or combination of both. Probably reserved-memory if you need the
kernel to access some of these regions.
Rob
[1] Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
--
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