Subject: Re: [PATCH net-next] net: phy: introduce phydev->port

From: Russell King - ARM Linux admin <[email-masked]>
Date: Wed, 10 Feb 2021 11:54:16 +0000

On Wed, Feb 10, 2021 at 12:20:02PM +0100, Michael Walle wrote:
> 
> Am 2021-02-09 17:38, schrieb Michael Walle:
> > --- a/drivers/net/phy/phy.c
> > +++ b/drivers/net/phy/phy.c
> > @@ -308,7 +308,7 @@ void phy_ethtool_ksettings_get(struct phy_device
> > *phydev,
> >  	if (phydev->interface == PHY_INTERFACE_MODE_MOCA)
> >  		cmd->base.port = PORT_BNC;
> >  	else
> > -		cmd->base.port = PORT_MII;
> > +		cmd->base.port = phydev->port;
> >  	cmd->base.transceiver = phy_is_internal(phydev) ?
> >  				XCVR_INTERNAL : XCVR_EXTERNAL;
> >  	cmd->base.phy_address = phydev->mdio.addr;
> 
> Russell, the phylink has a similiar place where PORT_MII is set. I don't
> know if we'd have to change that, too.

What would we change it to?

If there's no PHY attached and no SFP, what kind of interface do we
have? As we've no idea what's on the media side, assuming that we are
presenting a MII-like interface to stuff outside of what we control is
entirely reasonable.

Claiming the world is TP would be entirely wrong, there may not be a
RJ45 jack. Consider the case where the MAC is connected to a switch.
It's a MII-like link. It's certianly not TP, BNC, fiber, AUI, or
direct attach.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!