[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210720143046.GU22278@shell.armlinux.org.uk>
Date: Tue, 20 Jul 2021 15:30:46 +0100
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Andrew Lunn <andrew@...n.ch>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Marek Beh__n <kabel@...nel.org>,
Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH RFC net-next] net: phy: marvell10g: add downshift tunable
support
On Tue, Jul 20, 2021 at 04:28:12PM +0200, Andrew Lunn wrote:
> > +static int mv3310_set_downshift(struct phy_device *phydev, u8 ds)
> > +{
> > + struct mv3310_priv *priv = dev_get_drvdata(&phydev->mdio.dev);
> > + u16 val;
> > + int err;
> > +
> > + /* Fails to downshift with v0.3.5.0 and earlier */
> > + if (priv->firmware_ver < MV_VERSION(0,3,5,0))
> > + return -EOPNOTSUPP;
> > +
> > + if (ds == DOWNSHIFT_DEV_DISABLE)
> > + return phy_clear_bits_mmd(phydev, MDIO_MMD_PCS, MV_PCS_DSC1,
> > + MV_PCS_DSC1_ENABLE);
> > +
> > + /* FIXME: The default is disabled, so should we disable? */
> > + if (ds == DOWNSHIFT_DEV_DEFAULT_COUNT)
> > + ds = 2;
>
> Interesting question.
>
> It is a useful feature, so i would enable it by default.
>
> Is it possible to read the actual speed via some vendor register? The
> phy-core might then give a warning, but it is 50/50 since the link
> peer might perform the downshift.
We already do read the actual negotiated speed anbd other parameters
from the MV_PCS_CSSR1 register.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists