Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: Aleksei Sviridkin <f@lex.la>,
	chester.a.unal@arinc9.com, daniel@makrotopia.org, andrew@lunn.ch,
	olteanv@gmail.com, nbd@nbd.name, lorenzo@kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	vladislav.karmanov.dev@gmail.com
Cc: linux@armlinux.org.uk, dqfext@gmail.com, matthias.bgg@gmail.com,
	angelogioacchino.delregno@collabora.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net v5 1/2] net: dsa: mt7530: populate lpi_interfaces to fix EEE support
Date: Sat, 5 Sep 2026 01:10:33 +0200	[thread overview]
Message-ID: <780c9e93-ca6d-4481-8709-c8e5058f0073@wp.pl> (raw)
In-Reply-To: <20260903123644.23800-2-f@lex.la>

Hi Aleksei,
I'm a little confused by this patch. At the same time, there are patches
floating around mailing list to disable EEE on the MT7530 PHY[1]. Does
the EEE work, or is it broken?

1. 
https://patchwork.kernel.org/project/netdevbpf/patch/20260904202800.3410838-1-vladislav.karmanov.dev@gmail.com/

Best regards,
Aleksander

On 03/09/2026 14:36, Aleksei Sviridkin wrote:
> phylink_create() decides once and for all that a MAC supports managed
> EEE, and it requires the tx_lpi ops plus non-empty lpi_capabilities and
> lpi_interfaces. mt753x_phylink_get_caps() leaves lpi_interfaces empty.
>
> So ever since the conversion to phylink managed EEE, ethtool has
> answered "Not supported" on every mt753x port, and phy_disable_eee()
> has locked userspace out of turning EEE on. That undoes what
> commit 06dfcd4098cf ("net: dsa: mt7530: fix enabling EEE on MT7531
> switch on all boards") arranged: EEE off by default, but reachable
> with ethtool.
>
> Leave the speeds above 1 Gbps out of both bitmaps. PMCR folds
> SPEED_2500 and SPEED_10000 onto PMCR_FORCE_SPEED_1000, so
> PMCR_FORCE_EEE1G would govern LPI on such a link, and that is
> unvalidated rather than known unsupported: MediaTek's SDK driver sets
> the EEE force bits for 100 Mbps and 1 Gbps only, and the unit of the
> wakeup timers is undocumented with the port clock at 2.5 times the
> rate.
>
> LPI stays off until userspace enables it, but the EEE advertisement of
> a PHY that advertises it out of reset comes back, since phylink stops
> force-clearing it.
>
> Fixes: 9cf21773f535 ("net: dsa: mt7530: convert to phylink managed EEE")
> Signed-off-by: Aleksei Sviridkin <f@lex.la>
> ---
> Ports that support neither 100 Mbps nor 1 Gbps are skipped because on
> MT7988, EN7581 and AN7583 port 6 is 10 Gbps only and shares
> PHY_INTERFACE_MODE_INTERNAL with the user ports, so the interface mask
> alone cannot tell them apart. MT7531's internal PHYs keep the
> advertisement mt7531_setup() zeroed and EN7528 keeps both bitmaps
> empty, so EEE stays fully off there.
>
> Two pre-existing things this patch makes live, neither addressed here:
>
> - The unit of LPI_THRESH is still unspecified, as the comment above
>    lpi_timer_default says. Before the phylink conversion
>    mt753x_set_mac_eee() wrote tx_lpi_timer into the field directly, so
>    the raw unit has always been what ethtool showed on these ports.
>
> - mt753x_phylink_mac_enable_tx_lpi() sets the PMCR force-EEE bits
>    without checking the resolved speed or interface, relying entirely on
>    phylink never calling it above 1 Gbps. A check there would make the
>    driver robust independently of lpi_interfaces being right.
>
> v2, with the full argument for leaving the higher speeds out:
> https://lore.kernel.org/netdev/20260824024117.46154-2-f@lex.la/
>
> v4: lpi_capabilities is mac_capabilities masked to the two speeds
> instead of both asserted. Every port that reaches the guard today has
> both speeds, so nothing changes; it only stops the bitmap from claiming
> a speed a port cannot link at.
>
> v5: comments cut to one line (Maxime Chevallier); no code change.
>
>   drivers/net/dsa/mt7530.c | 16 ++++++++++++----
>   1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/dsa/mt7530.c b/drivers/net/dsa/mt7530.c
> index 2b7be091c056..3e61eb3c2b1e 100644
> --- a/drivers/net/dsa/mt7530.c
> +++ b/drivers/net/dsa/mt7530.c
> @@ -3172,23 +3172,31 @@ static void mt753x_phylink_get_caps(struct dsa_switch *ds, int port,
>   
>   	config->mac_capabilities = MAC_ASYM_PAUSE | MAC_SYM_PAUSE;
>   
> +	priv->info->mac_port_get_caps(ds, port, config);
> +
>   	/* The EN7528 GPHYs report EEE capability, but negotiating EEE with
>   	 * common link partners (e.g. Realtek GbE NICs) results in an unstable
>   	 * link with dropped frames. Leave the LPI capabilities empty so that
>   	 * phylink disables EEE on these PHYs and refuses to enable it from
>   	 * userspace.
>   	 */
> -	if (priv->id != ID_EN7528) {
> +	if (priv->id != ID_EN7528 &&
> +	    config->mac_capabilities & (MAC_100FD | MAC_1000FD)) {
>   		u32 eeecr = mt7530_read(priv, MT753X_PMEEECR_P(port));
>   
> -		config->lpi_capabilities = MAC_100FD | MAC_1000FD | MAC_2500FD;
> +		/* LPI above 1 Gbps is not supported */
> +		config->lpi_capabilities = config->mac_capabilities &
> +					   (MAC_100FD | MAC_1000FD);
> +		phy_interface_copy(config->lpi_interfaces,
> +				   config->supported_interfaces);
> +		__clear_bit(PHY_INTERFACE_MODE_2500BASEX,
> +			    config->lpi_interfaces);
> +
>   		/* tx_lpi_timer should be in microseconds. The time units for
>   		 * LPI threshold are unspecified.
>   		 */
>   		config->lpi_timer_default = FIELD_GET(LPI_THRESH_MASK, eeecr);
>   	}
> -
> -	priv->info->mac_port_get_caps(ds, port, config);
>   }
>   
>   static int mt753x_pcs_validate(struct phylink_pcs *pcs,


  reply	other threads:[~2026-09-05  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 12:36 [PATCH net v5 0/2] net: restore EEE on MediaTek switches and SoC MACs Aleksei Sviridkin
2026-09-03 12:36 ` [PATCH net v5 1/2] net: dsa: mt7530: populate lpi_interfaces to fix EEE support Aleksei Sviridkin
2026-09-04 23:10   ` Aleksander Jan Bajkowski [this message]
2026-09-04 23:24     ` Aleksei Sviridkin
2026-09-03 12:36 ` [PATCH net v5 2/2] net: ethernet: mtk_eth_soc: " Aleksei Sviridkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=780c9e93-ca6d-4481-8709-c8e5058f0073@wp.pl \
    --to=olek2@wp.pl \
    --cc=andrew@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chester.a.unal@arinc9.com \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=edumazet@google.com \
    --cc=f@lex.la \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=lorenzo@kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vladislav.karmanov.dev@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox