[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f7b894d0-9378-4c4d-8a3e-e35bb9593c72@lunn.ch>
Date: Tue, 26 Dec 2023 18:00:17 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Jagan Teki <jagan@...rulasolutions.com>,
Heiner Kallweit <hkallweit1@...il.com>,
"Andrew F. Davis" <afd@...com>,
Florian Fainelli <f.fainelli@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
Michael Nazzareno Trimarchi <michael@...rulasolutions.com>,
Ioana Ciornei <ioana.ciornei@....com>,
Shawn Guo <shawnguo@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Fabio Estevam <festevam@...il.com>
Subject: Re: PHY issue with SJA1105Q/DP84849I Design
> The code which should have prevented this from happening is in
> phy_attach_direct():
>
> if (phydev->attached_dev) {
> dev_err(&dev->dev, "PHY already attached\n");
> err = -EBUSY;
> goto error;
> }
The problem might be dsa_shared_port_phylink_register():
err = phylink_of_phy_connect(dp->pl, port_dn, 0);
if (err && err != -ENODEV) {
pr_err("could not attach to PHY: %d\n", err);
goto err_phy_connect;
}
return 0;
Since it is not -ENODEV, it just keep going.
Andrew
Powered by blists - more mailing lists