From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Li Yang <leoli-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: The usage of compatible 'simple-bus'
Date: Wed, 7 Jan 2009 09:25:51 -0600 [thread overview]
Message-ID: <20090107152551.GA15585@ld0162-tx32.am.freescale.net> (raw)
In-Reply-To: <2a27d3730901061951g333d10b6mf4dc0219570e521b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, Jan 07, 2009 at 11:51:12AM +0800, Li Yang wrote:
> > 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?
>
> Yes, we can use good old way. But as Scott has moved the MDIO into
> the gianfar node on MPC8313, maybe it's a better way to describe the
> relationship of the two parts.
Ah, right, that was to reflect the clock domain situation so that someday
when I get time to do device power management the kernel can know that by
shutting down ethernet@25000 it's also shutting down mdio@24520, which is
also used by ethernet@26000.
Adding simple-bus was a bit of a hack, but it preserves the existing
binding whereby mdio sits under a simple-bus. Ideally, the mdio node
would simply be a container for PHY nodes, and would simply be a part of
gianfar rather than a separate entity.
-Scott
next prev parent reply other threads:[~2009-01-07 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A45394FD742FA419B760BB8D398F9ED0B37E7@zch01exm26.fsl.freescale.net>
[not found] ` <3A45394FD742FA419B760BB8D398F9ED0B37E7-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2009-01-05 19:20 ` The usage of compatible 'simple-bus' Scott Wood
[not found] ` <20090105192053.GB23766-VKaLA/mbEU932VTgPCOETVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2009-01-06 1:43 ` David Gibson
2009-01-06 5:46 ` Li Yang
[not found] ` <20090106014323.GB29456-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2009-01-06 5:46 ` Li Yang
[not found] ` <3A45394FD742FA419B760BB8D398F9ED0B38C9@zch01exm26.fsl.freescale.net>
[not found] ` <3A45394FD742FA419B760BB8D398F9ED0B38C9-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2009-01-06 6:35 ` Grant Likely
[not found] ` <fa686aa40901052235t1342b6e2w4fde664f1ebb3aa3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-06 7:01 ` Li Yang
2009-01-07 2:00 ` David Gibson
2009-01-07 2:00 ` David Gibson
[not found] ` <20090107020006.GD13731@yookeroo.seuss>
2009-01-07 3:26 ` Grant Likely
[not found] ` <20090107020006.GD13731-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2009-01-07 3:26 ` Grant Likely
2009-01-07 3:51 ` Li Yang
[not found] ` <2a27d3730901061951g333d10b6mf4dc0219570e521b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-07 15:25 ` Scott Wood [this message]
2009-01-05 10:27 Li Yang
-- strict thread matches above, loose matches on Subject: below --
2009-01-05 10:27 Li Yang
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=20090107152551.GA15585@ld0162-tx32.am.freescale.net \
--to=scottwood-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=leoli-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.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