From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM i.MX51: Add Digi ConnectCore devicetree
Date: Wed, 2 Apr 2014 20:47:11 +0800 [thread overview]
Message-ID: <20140402124710.GC10283@dragon> (raw)
In-Reply-To: <1396440407.634334403@f167.i.mail.ru>
On Wed, Apr 02, 2014 at 04:06:47PM +0400, Alexander Shiyan wrote:
> > > > > +&weim {
> > > > > + pinctrl-names = "default";
> > > > > + pinctrl-0 = <&pinctrl_weim>;
> > > > > + status = "okay";
> > > > > +
> > > > > + lan9221: lan9221 at ce000000 {
> > > >
> > > > How does 'ce000000' in the node name comes?
> > >
> > > This is a WEIM CS5 start address.
> >
> > Hmm, shouldn't the unit-address come from the 'reg' property of the node
> > somehow?
>
> I'm not sure. Here is the real physical address of the device, in the case of
> using an address from the "reg", we get zero address.
>
> Just imagine, that we have a second LAN chip on the start of CS4.
> Two identical devices?
The node name should be 'lan9221 at 5,0' and 'lan9221 at 4,0' respectively.
Shawn
next prev parent reply other threads:[~2014-04-02 12:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 6:48 [PATCH] ARM: dts: imx27-phytec-phycore-rdk: Add display control signal definitions Alexander Shiyan
2014-03-29 6:48 ` [PATCH] ARM i.MX51: Add Digi ConnectCore devicetree Alexander Shiyan
2014-04-02 11:39 ` Shawn Guo
2014-04-02 11:45 ` Alexander Shiyan
2014-04-02 11:56 ` Shawn Guo
2014-04-02 12:06 ` Alexander Shiyan
2014-04-02 12:47 ` Shawn Guo [this message]
2014-04-02 12:56 ` Alexander Shiyan
2014-04-02 13:20 ` Shawn Guo
2014-04-02 12:53 ` Sascha Hauer
2014-04-02 17:44 ` Robert Schwebel
2014-04-02 17:59 ` Dirk Behme
2014-04-02 18:08 ` Alexander Shiyan
2014-04-03 6:49 ` Sascha Hauer
2014-04-02 11:25 ` [PATCH] ARM: dts: imx27-phytec-phycore-rdk: Add display control signal definitions 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=20140402124710.GC10283@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;
as well as URLs for NNTP newsgroup(s).