[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b3e4339-93d5-4d14-b53f-43c5d379d2fa@lunn.ch>
Date: Tue, 2 Sep 2025 17:08:39 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "G Thomas, Rohan" <rohan.g.thomas@...era.com>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>,
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>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Matthew Gerlach <matthew.gerlach@...era.com>
Subject: Re: [PATCH net-next] net: phy: marvell: Fix 88e1510 downshift
counter errata
> > Also, what is a "link power down/up" ? Are you referring to setting
> > BMCR_PDOWN and then clearing it? (please update the commit description
> > and repost after 24 hours, thanks.)
> >
>
> Yes, I'm referring to setting and the clearing BMCR_PDOWN. Will update
> the commit description in the next version.
So it could be the bootloader left the PHY in powered down state, when
booting.
There is some not so nice logic in phy_attach_direct() which calls
phy_resume() when the MAC attaches to the PHY. So this case is covered
by that. But it would be good to comment in the commit message, and
maybe the resume function, that you are relying on this behaviour.
I do wounder if it should be more explicit, m88e1510_config_init()
also calls the workaround? You would then not need the comment.
Andrew
Powered by blists - more mailing lists