On 06/14/2016 03:44 PM, Sergei Shtylyov wrote:
On 06/14/2016 07:16 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)...
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.
