[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PAXPR04MB8510028FA548562F1A7B7A1688112@PAXPR04MB8510.eurprd04.prod.outlook.com>
Date: Tue, 7 Jan 2025 02:19:53 +0000
From: Wei Fang <wei.fang@....com>
To: Heiner Kallweit <hkallweit1@...il.com>, Vladimir Oltean
<vladimir.oltean@....com>, Claudiu Manoil <claudiu.manoil@....com>, Clark
Wang <xiaoning.wang@....com>, Russell King - ARM Linux
<linux@...linux.org.uk>, Andrew Lunn <andrew@...n.ch>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "imx@...ts.linux.dev"
<imx@...ts.linux.dev>
Subject: RE: EEE unsupported on enetc
> > In enetc_phylink_connect() we have the following:
> >
> > /* disable EEE autoneg, until ENETC driver supports it */
> > memset(&edata, 0, sizeof(struct ethtool_keee));
> > phylink_ethtool_set_eee(priv->phylink, &edata);
> >
> > Is it a hw constraint (if yes, on all IP versions?) that EEE isn't supported,
> > or is just some driver code for lpi timer handling missing?
> > Any plans to fix EEE in this driver?
>
> Hi Heiner,
>
> Currently, there are two platforms use the enetc driver, one is LS1028A,
> whose ENETC version is v1.0, and the other is i.MX95, whose version is
> v4.1. As far as I know, the ENETC hardware of both platforms supports
> EEE, but the implementation is different. As the maintainer of i.MX
> platform, I definitely sure Clark will add the EEE support for i.MX95 in the
> future. But for LS1028A, it is not clear to me whether Vladimir has plans
> to support EEE.
By the way, I am confirming with NETC architect internally whether LS1028A
ENETC supports dynamic LPI mode like i.MX95 (RM does not indicate this,
but the relevant registers exist). If it does, we can add EEE support to
LS1028A and i.MX95 together.
Powered by blists - more mailing lists