On 06/14/2016 01:42 PM, Andrew Lunn wrote:
On Tue, Jun 14, 2016 at 11:16:02AM -0500, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
internal phy, then we need to poll the phy to reliably detect
phy state changes.
Hi Jeremy
Why does the external phy not have the exact same problem?
Hello,
It may... but I've only got a fairly limited hardware testing setup, and
this driver is used across a pretty broad set of hardware configured in
various ways. So, I'm trying to limit the scope of things I might break.
Initially I thought it was added to avoid a QEMU issue, but now I don't
think that is the case.
So, if 0 can't be an interrupt why not update phy_interrupt_is_valid()
to check for it? That would fix the problem too...
