From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX DT memory nodes
Date: Wed, 12 Sep 2018 10:39:05 +0800 [thread overview]
Message-ID: <20180912023902.GA28239@dragon> (raw)
In-Reply-To: <CAL_JsqKtwt39k95d32ni=mKrZ=UVmTBH_onxC3ncjWs9eLbdJw@mail.gmail.com>
On Tue, Sep 11, 2018 at 04:54:40PM -0500, Rob Herring wrote:
> It appears that many i.MX platforms have duplicate, incomplete memory
> nodes with both "memory" and "memory@<addr>" nodes. Are you all aware
> of this? Plan to fix it? I guess u-boot fixes things enough to work.
@Fabio, it seems that the most of them are caused by the empty 'memory'
node in <soc>.dtsi. Can these be removed now?
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Rob Herring <robh@kernel.org>, Fabio Estevam <fabio.estevam@nxp.com>
Cc: devicetree@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: i.MX DT memory nodes
Date: Wed, 12 Sep 2018 10:39:05 +0800 [thread overview]
Message-ID: <20180912023902.GA28239@dragon> (raw)
In-Reply-To: <CAL_JsqKtwt39k95d32ni=mKrZ=UVmTBH_onxC3ncjWs9eLbdJw@mail.gmail.com>
On Tue, Sep 11, 2018 at 04:54:40PM -0500, Rob Herring wrote:
> It appears that many i.MX platforms have duplicate, incomplete memory
> nodes with both "memory" and "memory@<addr>" nodes. Are you all aware
> of this? Plan to fix it? I guess u-boot fixes things enough to work.
@Fabio, it seems that the most of them are caused by the empty 'memory'
node in <soc>.dtsi. Can these be removed now?
Shawn
next prev parent reply other threads:[~2018-09-12 2:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 21:54 i.MX DT memory nodes Rob Herring
2018-09-11 21:54 ` Rob Herring
2018-09-12 2:38 ` Fabio Estevam
2018-09-12 2:38 ` Fabio Estevam
2018-09-12 2:52 ` Rob Herring
2018-09-12 2:52 ` Rob Herring
2018-09-12 2:39 ` Shawn Guo [this message]
2018-09-12 2:39 ` Shawn Guo
2018-09-12 2:54 ` Fabio Estevam
2018-09-12 2:54 ` Fabio Estevam
2018-11-29 20:10 ` Rob Herring
2018-11-29 20:10 ` Rob Herring
2018-11-29 21:37 ` Fabio Estevam
2018-11-29 21:37 ` Fabio Estevam
2018-11-29 22:21 ` Rob Herring
2018-11-29 22:21 ` Rob Herring
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=20180912023902.GA28239@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.