[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTik7xeMnx0S2m0easY0hVT_UmomjzA@mail.gmail.com>
Date: Fri, 15 Apr 2011 15:29:55 -0500
From: Andy Fleming <afleming@...il.com>
To: ANDY KENNEDY <ANDY.KENNEDY@...ran.com>
Cc: michael@...sch.at, netdev@...r.kernel.org
Subject: Re: SMSC 8720a/MDIO/PHY help.
On Wed, Apr 13, 2011 at 4:38 PM, ANDY KENNEDY <ANDY.KENNEDY@...ran.com> wrote:
>> -----Original Message-----
>> From: Michael Riesch [mailto:michael@...sch.at]
>> Sent: Wednesday, April 13, 2011 4:19 PM
>> To: netdev@...r.kernel.org
>> Cc: ANDY KENNEDY
>> Subject: Re: SMSC 8720a/MDIO/PHY help.
>>
>>
>> > If you have an idea of something for me to try, I'd love to
>> entertain
>> > it.
>>
>> I am rather new to PHYLIB, but these are my ideas:
>>
>> 1) make sure phy_connect is executed (AFIAK called by MDIO bus
>> driver)
>
> Going through the phy.txt doc under Documentation/networking:
> PHY Abstraction Layer
> (Updated 2008-04-08)
> though it may be a bit out-of-date, I did see what you are talking about. What I'm hung up on at the moment is the behavior of adjust_link(). It appears that I only need to start the queues, though I don’t know.
>
>>
>> 2) maybe you need to call phy_start / phy_stop (AFAIK from the PHY
>> driver's open / close function)
>
> Currently, when I do this I only get the call to adjust_link() over and over again.
...this means that the state machine is running. The PHY is polling
every couple seconds to report the current state. It calls
adjust_link() to keep the net_device up-to-date on that state. What
other behavior are you expecting to see?
Andy
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists