[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZWcGn7KVSpsN/1Ee@shell.armlinux.org.uk>
Date: Wed, 29 Nov 2023 09:38:39 +0000
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [net-next PATCH 08/14] net: phy: at803x: drop specific PHY id
check from cable test functions
On Wed, Nov 29, 2023 at 03:12:13AM +0100, Christian Marangi wrote:
> @@ -1310,10 +1302,6 @@ static int at803x_cable_test_start(struct phy_device *phydev)
> */
> phy_write(phydev, MII_BMCR, BMCR_ANENABLE);
> phy_write(phydev, MII_ADVERTISE, ADVERTISE_CSMA);
> - if (phydev->phy_id != ATH9331_PHY_ID &&
> - phydev->phy_id != ATH8032_PHY_ID &&
> - phydev->phy_id != QCA9561_PHY_ID)
> - phy_write(phydev, MII_CTRL1000, 0);
...
> +static int at8031_cable_test_start(struct phy_device *phydev)
> +{
> + at803x_cable_test_start(phydev);
> + phy_write(phydev, MII_CTRL1000, 0);
I don't think this is a safe change - same reasons as given on a
previous patch. You can't randomly reorder register writes like this.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists