[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <caa45a64-47de-4466-0923-de51a8a8d26a@cogentembedded.com>
Date: Wed, 15 Jun 2016 00:24:33 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: Jeremy Linton <jeremy.linton@....com>, netdev@...r.kernel.org
Cc: steve.glendinning@...well.net
Subject: Re: [PATCH] net: smsc911x: If PHY doesn't have an interrupt then POLL
On 06/14/2016 11:59 PM, Jeremy Linton wrote:
>>> If the interrupt configuration isn't set and we are using the
>>
>> It's never set, judging by the driver code.
>>
>>> internal phy, then we need to poll the phy to reliably detect
>>> phy state changes.
>>
>> What address your internal PHY is at? Mine is at 1, and things seem
>> to work reliably after probing:
>>
>> SMSC LAN8700 18000000.etherne:01: attached PHY driver [SMSC LAN8700]
>> (mii_bus:phy_addr=18000000.etherne:01, irq=-1)
>
> Looks like your phy ends up polling (-1==IRQ_POLL)...
Yeah. You didn't answer my question though...
>> I'm using the device tree on my board.
>
> This was DT as well with a recent fedora/NetworkManager. It actually seems
> to be timing related to how fast the device gets configured after the initial
> phy probe. There is something like a 1 second window or so where it will work,
> but if network manager takes longer than that, the link state drops and cannot
> be brought back up unless the cable is pulled, replugged while the netdevice
> is being restarted.
1 second is the PHY poll interval IIRC.
MBR, Sergei
Powered by blists - more mailing lists