From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx28-evk: Fix display duplicate name warning
Date: Mon, 25 Aug 2014 10:44:35 +0800 [thread overview]
Message-ID: <20140825024434.GJ2540@dragon> (raw)
In-Reply-To: <CAOMZO5DySdUd8j583jEGCgX0oG8i8i1488M6MER-7Ys23fQ0Nw@mail.gmail.com>
On Sun, Aug 24, 2014 at 11:34:31PM -0300, Fabio Estevam wrote:
> On Sun, Aug 24, 2014 at 11:27 PM, Shawn Guo <shawn.guo@freescale.com> wrote:
>
> > Unit address only makes sense where parent has #address-cells and
> > #size-cells and the node itself has 'reg' property.
>
> Ok, I followed the way arch/arm/boot/dts/imx28-tx28.dts implemented
> the display node.
>
> > I guess it's more appropriate to name the node in particular display
> > device model that the node is defining?
>
> Sorry, I did not understand. Could you please provide an example for
> clarification?
See LVDS panel example in arch/arm/boot/dts/imx6qdl-sabresd.dtsi
Shawn
prev parent reply other threads:[~2014-08-25 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 1:59 [PATCH] ARM: dts: imx28-evk: Fix display duplicate name warning Fabio Estevam
2014-08-25 2:27 ` Shawn Guo
2014-08-25 2:34 ` Fabio Estevam
2014-08-25 2:44 ` Shawn Guo [this message]
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=20140825024434.GJ2540@dragon \
--to=shawn.guo@freescale.com \
--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