All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC][RFC] MPC8360E-RDK: Device tree and board file
Date: Tue, 18 Dec 2007 19:51:35 +0300	[thread overview]
Message-ID: <20071218165135.GA32585@localhost.localdomain> (raw)
In-Reply-To: <4767F271.4090703@freescale.com>

On Tue, Dec 18, 2007 at 10:16:49AM -0600, Scott Wood wrote:
> David Gibson wrote:
> >In this case the driver and binding have been developed together and
> >for the time being it does require PHY nodes, obviously.  I'm saying
> >that maybe that requirement ought to be changed.
> 
> I don't see why.
> 
> >Well, phandle is only used to find the phy node itself, so it doesn't
> >count.  The only piece of information there is the reg - the PHY id.
> >Following a phandle to another node is a fairly complex way of finding
> >a single integer.  
> >
> >Eh, I guess it's ok, but just directly giving the PHY id or a probe
> >mask in the MAC node would also be fine (we do this for 4xx EMAC).
> 
> It's not just a simple integer -- it also tells you which mdio bus it's on.

Exactly. And at least one board (MPC8568E-MDS) using this feature:
UECs are using PHYs placed on the TSEC's MDIO bus. This is hardware
configurable, and could be contrariwise: TSECs can use PHYs that
are under control of UEC MDIO bus controller.

That's why we're naming PHYs as bus:phyid.

-- 
Anton Vorontsov
email: cbou@mail.ru
backup email: ya-cbou@yandex.ru
irc://irc.freenode.net/bd2

  reply	other threads:[~2007-12-18 16:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 20:29 [PATCH] [POWERPC][RFC] MPC8360E-RDK: Device tree and board file Anton Vorontsov
2007-12-11  0:30 ` Stephen Rothwell
2007-12-11 17:19   ` Anton Vorontsov
2007-12-11 18:42 ` Kumar Gala
2007-12-15 16:23   ` Anton Vorontsov
2007-12-17  5:14     ` David Gibson
2007-12-17 17:03       ` Scott Wood
2007-12-17 17:10         ` Kim Phillips
2007-12-17 17:20           ` Scott Wood
2007-12-17 17:42             ` Kim Phillips
2007-12-17 18:26         ` Vitaly Bordug
2007-12-17 18:48           ` Scott Wood
2007-12-17 20:55             ` Vitaly Bordug
2007-12-18  3:51         ` David Gibson
2007-12-18 16:16           ` Scott Wood
2007-12-18 16:51             ` Anton Vorontsov [this message]
2007-12-18 22:39             ` David Gibson
2007-12-19 13:05         ` Anton Vorontsov
2007-12-19 16:15           ` Scott Wood
2007-12-19 16:36             ` Anton Vorontsov
2007-12-19 20:59         ` Anton Vorontsov
2007-12-18 15:53     ` Kumar Gala

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=20071218165135.GA32585@localhost.localdomain \
    --to=avorontsov@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=sfr@canb.auug.org.au \
    /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.