All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question: Information regarding MII and PHY
Date: Thu, 22 Sep 2011 18:21:39 -0400	[thread overview]
Message-ID: <201109221821.40781.vapier@gentoo.org> (raw)
In-Reply-To: <CALButCJ2Ni5R073q7q2eQTCDb8gCBdyhh3PWw-bNj3GzLoPa-Q@mail.gmail.com>

On Wednesday, September 21, 2011 23:12:44 Graeme Russ wrote:
> On Thu, Sep 22, 2011 at 11:20 AM, Graeme Russ wrote:
> > descriptions, mentions MII/GMII and PHY support (but not much on the
> > specifics). Now in U-Boot there appears to be a common set of code
> > relating to PHY and MII. There appears to be a mix of Ethernet drivers
> > that use MII/PHY and drivers that do not, but I cannot seems to quite
> > get me head around it all. One weird thing is that there does not
> > appear to be any granular inclusion of PHY drivers -
> > /include/config_phylib_all_drivers.h defines them all when
> > CONFIG_PHYLIB is defined, but I could not find any boards that defined
> > just one PHY driver. I also cannot find how MII/PHY functions interact
> > with PCI for PCI based cards.
> 
> I now see why there is no relationship between MII/PHY and PCI as they are
> not connected to the PCI bus - Communication with the PHY is done through
> the MAC. So is it the case that 'PHY Drivers' in U-Boot provide access
> to the PHY (Transceiver) _through_ the MAC and in order to use the PHY
> drivers, the MAC driver (i.e. the Ethernet driver) needs to provide hooks
> to pass PHY requests from U-Boot over the (RG)MII interface?

i believe this is correct.  the intention is to be like Linux where you've got 
a driver for the MAC, and you've got drivers for the PHYs, and the MAC driver 
provides the hooks for the PHY layer to access what it needs.

not all drivers have been converted to the PHY abstraction, and we don't have 
a requirement atm for that.

there's also a bit of a mess as we try to move to the Linux phylib code ... 
another area that needs a bit of TLC.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110922/16378280/attachment.pgp 

  reply	other threads:[~2011-09-22 22:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22  1:20 [U-Boot] Question: Information regarding MII and PHY Graeme Russ
2011-09-22  3:12 ` Graeme Russ
2011-09-22 22:21   ` Mike Frysinger [this message]
2011-09-22 23:06     ` Graeme Russ
2011-09-22 23:27     ` Graeme Russ
2011-09-22 23:36       ` Andy Fleming
2011-09-23  0:17         ` Graeme Russ
2011-09-23  1:23           ` Mike Frysinger
2011-09-27 16:32           ` Andy Fleming
2011-09-22 23:30 ` Andy Fleming

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=201109221821.40781.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /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.