On 8/9/23 15:40, Andrew Lunn wrote:
quoted
quoted
Hm.. how about officially defining this PHY as the clock provider and disable
PHY automatic hibernation as long as clock is acquired?
Sorry, I don't know much about the clock provider/consumer, but I think there
will be more changes if we use clock provider/consume mechanism.
Less changes is not always best. What happens when a different PHY is
used?
Then the system wouldn't be affected by this AR803x specific behavior.
By having a clock provider in the PHY, you are defining a clear
API that any PHY needs to provide to work with this MAC.
As Russell has point out, this is not the first time we have run into
this problem. So far, it seems everybody has tried to solve it for
just their system. So maybe now we should look at the whole picture
and put in place a generic solution which can be made to work for any
PHY.
I'll see what I can do, it might take a while though.