From: Florian Fainelli
Date: Sat, 21 Oct 2017 19:01:45 -0700
> Reviewed-by : Florian Fainelli
>
> I still can't make sure this is not a problem for multiple PHYs
> hanging off the same bus, but like anything else, we'll deal with
> problems later if they arise.
Thanks Florian.
Applied, thanks
On October 21, 2017 6:37:38 PM PDT, David Miller wrote:
>
>Second ping, this patch needs a review ASAP.
>
>Geert's hard-resetting PHY changes depend upon this change.
Done, same concerns as before and we could all improve on trying to get this
tested on a pure SW model (e.g QEMU) but there is on
On October 18, 2017 4:54:03 AM PDT, Geert Uytterhoeven
wrote:
>If an Ethernet PHY is initialized before the interrupt controller it is
>connected to, a message like the following is printed:
>
>irq: no irq domain found for /interrupt-controller@e61c !
>
>However, the actual error is ignor
Second ping, this patch needs a review ASAP.
Geert's hard-resetting PHY changes depend upon this change.
Thank you.
From: Geert Uytterhoeven
Date: Wed, 18 Oct 2017 13:54:03 +0200
> The actual patch is unchanged since v1, sent on May 18. Obviously I
> still cannot test it on a system with multiple PHYs, just like v1.
>
> How can we proceed?
Andrew and Florian, please review this.
If an Ethernet PHY is initialized before the interrupt controller it is
connected to, a message like the following is printed:
irq: no irq domain found for /interrupt-controller@e61c !
However, the actual error is ignored, leading to a non-functional (POLL)
PHY interrupt later:
Micre
