From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: mx5: Pass the memory unit-address
Date: Thu, 1 Mar 2018 08:41:41 +0800 [thread overview]
Message-ID: <20180301004139.GN3217@dragon> (raw)
In-Reply-To: <CAOMZO5DDf7nRM0UQRiyEKwc=7Ta-s-yExgUhrxt8=QRZBqJ5MQ@mail.gmail.com>
On Wed, Feb 28, 2018 at 09:00:50AM -0300, Fabio Estevam wrote:
> Hi Shawn,
>
> On Wed, Feb 28, 2018 at 12:03 AM, Shawn Guo <shawnguo@kernel.org> wrote:
>
> > One thing I'm unsure is which memory node will be fixed up with correct
> > memory configuration, considering we will have two memory nodes. One is
> > the following that defined in imx51.dtsi.
> >
> > memory { device_type = "memory"; };
> >
> > And the other is memory at 90000000.
>
> On my tests the correct memory@ is filled with the real memory size.
>
> One further cleanup I can make to avoid this double memory node is:
>
> --- a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> @@ -20,6 +20,7 @@
> };
>
> memory at 10000000 {
> + device_type = "memory";
> reg = <0x10000000 0x40000000>;
> };
>
> diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
> index c003e62..f3376f0 100644
> --- a/arch/arm/boot/dts/imx6qdl.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl.dtsi
> @@ -23,7 +23,6 @@
> * Also for U-Boot there must be a pre-existing /memory node.
> */
> chosen {};
> - memory { device_type = "memory"; };
>
> aliases {
> ethernet0 = &fec;
>
> If you agree I can do this for all i.MX dts.
>
> What do you think?
I agree. In the end, we will need to have every single board DTS
contain a memory at unit-address node. Although the size field can be
dummy and fixed up by bootloader.
Shawn
next prev parent reply other threads:[~2018-03-01 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 2:13 [PATCH] ARM: dts: mx5: Pass the memory unit-address Fabio Estevam
2018-02-28 3:03 ` Shawn Guo
2018-02-28 12:00 ` Fabio Estevam
2018-03-01 0:41 ` Shawn Guo [this message]
2018-03-01 0:43 ` Shawn Guo
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=20180301004139.GN3217@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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