[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aA_DyKw8AVPdmu-Y@pengutronix.de>
Date: Mon, 28 Apr 2025 20:07:04 +0200
From: Oleksij Rempel <o.rempel@...gutronix.de>
To: Andrew Lunn <andrew@...n.ch>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Florian Fainelli <f.fainelli@...il.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Vladimir Oltean <olteanv@...il.com>,
Woojung Huh <woojung.huh@...rochip.com>,
"Russell King (Oracle)" <linux@...linux.org.uk>,
Heiner Kallweit <hkallweit1@...il.com>, stable@...r.kernel.org,
kernel@...gutronix.de, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net v1 1/2] net: dsa: microchip: let phylink manage PHY
EEE configuration on KSZ switches
On Mon, Apr 28, 2025 at 06:51:19PM +0200, Andrew Lunn wrote:
> > +/**
> > + * ksz_phylink_mac_disable_tx_lpi() - Dummy handler to disable TX LPI
> > + * @config: phylink config structure
> > + *
> > + * For ports with integrated PHYs, LPI is managed internally by hardware.
>
> Could you expand that.
>
> Does it mean the hardware will look at the results of the autoneg and
> disable/enable LPI depending on those results?
Yes.
> I also assume this means it is not possible to force LPI on/off, independent
> of autoneg?
Correct. set_eee call in this driver is filtering (tx_lpi == false) to
reflect HW functionality.
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists