linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Li Yang" <LeoLi@freescale.com>,
	"Wood Scott-B07421" <scottwood@freescale.com>,
	linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: The usage of compatible 'simple-bus'
Date: Tue, 6 Jan 2009 20:26:31 -0700	[thread overview]
Message-ID: <fa686aa40901061926o6858602em60281a1e39daa0c2@mail.gmail.com> (raw)
In-Reply-To: <20090107020006.GD13731@yookeroo.seuss>

On Tue, Jan 6, 2009 at 7:00 PM, David Gibson
<david@gibson.dropbear.id.au> wrote:
> As Grant says, you're thinking about what drivers will do with things
> rather than what the actual hardware setup is, which is what the
> device tree should describe.
>
> I see two sensible options for this situation:
>        - Move the MDIO node to outside the gianfar MAC node.  I think
> this is already done on some boards with gianfar?

mpc5200 FEC is another example of this.

>        - Explicitly add the gianfar device to the list of things to
> scan for of_platform subdevices.

Ack.  I 100% agree.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2009-01-07  3:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 10:27 The usage of compatible 'simple-bus' Li Yang
2009-01-05 19:20 ` Scott Wood
2009-01-06  1:43   ` David Gibson
2009-01-06  5:46     ` Li Yang
2009-01-06  6:35       ` Grant Likely
2009-01-06  7:01         ` Li Yang
2009-01-07  2:00       ` David Gibson
2009-01-07  3:26         ` Grant Likely [this message]
2009-01-07  3:51         ` Li Yang
2009-01-07 15:25           ` Scott Wood

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=fa686aa40901061926o6858602em60281a1e39daa0c2@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=LeoLi@freescale.com \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).