Hello. On 8/14/2014 10:31 AM, leroy christophe wrote:
I have an hardware with two ethernet interfaces, and with the two PHYs inside the same component INTEL LXT973 which has only one interrupt. I also have another hardware with two ethernet interfaces and two independant PHYs. But the two PHYs are wired to the same interrupt. This is working perfectly up to Linux 3.12.
Hm, I'm surprised it works. Are you sure you're getting interrupts from both PHYs? Because if both Ethernet controllers are active simultaneously, only the first registered PHY IRQ handler should get all the interrupts.
But since your commit, introduced in Linux 3.13, my interfaces don't work anymore as the second PHYs can't register IRQ.
Strange too, the phylib should use polling in case request_irq() fails.
Reading the commit log, I can't really understand the reason for the change.
The shared IRQ handler should check for IRQ from its device and return IRQ_NONE if there's no IRQ active; phy_interrupt() doesn't do that (this is pushed to the workqueue).
Is it really worth it, and therefore how shall my case be handled ?
PHY IRQs are not necessary for the phylib state machine.
Christophe
WBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
