[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <022e19f5-9a9c-42eb-9358-a6fe832e8f5f@lunn.ch>
Date: Mon, 31 Mar 2025 00:01:20 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Lukasz Majewski <lukma@...x.de>
Cc: Andrew Lunn <andrew+netdev@...n.ch>, davem@...emloft.net,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
Richard Cochran <richardcochran@...il.com>, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 4/4] net: mtip: The L2 switch driver for imx287
> > > + /* Prevent a state halted on mii error */
> > > + if (fep->mii_timeout && phy_dev->state == PHY_HALTED) {
> > > + phy_dev->state = PHY_UP;
> > > + goto spin_unlock;
> > > + }
> >
> > A MAC driver should not be playing around with the internal state of
> > phylib.
>
> Ok, I've replaced it with PHY API calls (phy_start() and
> phy_is_started()).
phy_start() and phy_stop() should be used in pairs. It is not good to
call start more often than stop.
What exactly is going on here? Why would there be MII errors?
Andrew
Powered by blists - more mailing lists