netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Amy Fong <amy.fong@windriver.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH] Add Broadcom PHY support
Date: Tue, 05 Dec 2006 17:03:01 +1100	[thread overview]
Message-ID: <1165298581.29784.58.camel@localhost.localdomain> (raw)
In-Reply-To: <E1GrTGu-0005QS-OH@lucciola>


> I believe that this fiber enabling can be done by defining config_init in the phy_driver struct.
> 
> struct phy_driver {
> <snip>
>         /* Called to initialize the PHY,
> 	 * including after a reset */
> 	int (*config_init)(struct phy_device *phydev);
> <snip>
> };

Well... I don't know for sure... thing is, enabling the fiber mode is a
rather platform specific thing. So it's the MAC driver that knows wether
it wants it on a PHY and should call into the driver.

It's difficult to abstract all possible PHY config options tho... some
MACs might want to enable low power, some don't because they have issues
with it, that sort of thing, though.

Not sure what the best solution is at this point... Maybe an ascii
string to pass the PHY driver is the most flexible, though a bit yucky,
or we try to have a list of all the possible configuration options in
phy.h and people just add new ones that they need as they add support
for them...

Sounds grossly like an in-kernel ioctl tho...

Ben.



  reply	other threads:[~2006-12-05  6:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 20:15 [PATCH] Add Broadcom PHY support Amy Fong
2006-09-19  4:39 ` Jeff Garzik
2006-09-19 13:35   ` Amy Fong
2006-09-19 13:43     ` Maciej W. Rozycki
2006-09-19 16:45       ` Jeff Garzik
2006-09-19 17:10         ` Maciej W. Rozycki
2006-12-04 21:16 ` Benjamin Herrenschmidt
2006-12-05  5:55   ` Amy Fong
2006-12-05  6:03     ` Benjamin Herrenschmidt [this message]
2006-12-05 19:50       ` 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=1165298581.29784.58.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=amy.fong@windriver.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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).