This is all fine as long as Linux doesn't go and reset the phy again. Until
bafbdd527d56 ("phylib: Add device reset GPIO support") was the case. After
that commit I believe phylib is resetting the phy while attempting to enter
unmanaged mode, which is now allowed in this particular chip.
Since it appears the phy is not usually described by the device tree but is
instead discovered by probing a MII-based ID register, it seems the best
place to put this is within the phy driver itself. I find it's usually best
to describe things with code, so I hacked up something like
Talking to Florian, i was under the impression that you could not even
discover the device when its reset state what wrong. You could not
read the ID registers.
Your suggested change assumed you can discover the device. Is this
true?
Thanks
Andrew