Hi Andrew,

On 8/18/21 12:05 AM, Andrew Lunn wrote:

quoted

Do these integrated NXP PHYs use a specific PHY driver, or do they just
use the Generic PHY driver? If the former is the case, do you experience
that the PHY driver fails to get probed during mdiobus registration if
the kernel uses fw_devlink=on?

The Marvell mv88e6xxx driver registers upto two MDIO busses, and the
PHYs on those busses make use of the marvell PHY driver. I've not
tested specifically with fw_devlink=on, but in general, the Marvell
PHY driver does get bound to these devices.

Thanks for your reply. I should add that with fw_devlink=permissive, the 
PHY driver gets probed just fine. It's only since v5.13 that 
fw_devlink=on has been the default[1], so it may be something new to 
check. But if you think it's working for other drivers then that means I 
will have to look into further on my end.

Kind regards,
Alvin

[1] ea718c699055 ("Revert "Revert "driver core: Set fw_devlink=on by 
default""")
 
https://lore.kernel.org/lkml/20210302211133.2244281-4-saravanak@google.com/ (local)

     Andrew