> > > diff --git a/drivers/net/phy/phy-core.c b/drivers/net/phy/phy-core.c
> > > index a64186dc53f8..686a57d56885 100644
> > > --- a/drivers/net/phy/phy-core.c
> > > +++ b/drivers/net/phy/phy-core.c
> > > @@ -556,7 +556,7 @@ int __phy_read_mmd(struct phy_device
> > > *phydev, int devad, u32 regnum)
> > >
> > > if (phydev->drv && phydev->drv->read_mmd) {
> > > val = phydev->drv->read_mmd(phydev, devad, regnum);
> > > - } else if (phydev->is_c45) {
> > > + } else if (phy_has_c45_registers(phydev)) {
> >
> > This i would say should be
> >
> > phy_has_c45_transfers(phydev). This is about, can we do C45 transfers
> > on the bus, and if not, fall back to C45 over C22.
>
> Shouldn't this then be a bus property? I.e. mdiobus_has_c45_transfers().
> I've have a similar helper introduced in 9/11:
>
> static inline bool mdiobus_supports_c45(struct mii_bus *bus)
> {
> return bus->read_c45 && !bus->prevent_c45_access;
> }
In the case of the above (the code in __phy_read_mmd()), I wouldn't
at least initially change the test there.
phydev->is_c45 will only be true if we probed the PHY using clause
45 accesses. Thus, it will be set if "the bus supports clause 45
accesses" _and_ "the PHY responds to those accesses".
Changing that to only "the bus supports clause 45 accesses" means
that a PHY supporting only clause 22 access with indirect clause
45 access then fails if it's used with a bus that supports both
clause 22 and clause 45 accesses.