From: Andrew Lunn <andrew@lunn.ch>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Woojung Huh <woojung.huh@microchip.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Yuiko Oshino <yuiko.oshino@microchip.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
Phil Elwell <phil@raspberrypi.org>
Subject: Re: [PATCH net v1 2/2] net: phy: microchip: limit 100M workaround to link-down events on LAN88xx
Date: Wed, 9 Jul 2025 16:17:52 +0200 [thread overview]
Message-ID: <a6c2059c-487b-4e00-9399-b98d867168b5@lunn.ch> (raw)
In-Reply-To: <20250709130753.3994461-3-o.rempel@pengutronix.de>
On Wed, Jul 09, 2025 at 03:07:53PM +0200, Oleksij Rempel wrote:
> Restrict the 100Mbit forced-mode workaround to link-down transitions
> only, to prevent repeated link reset cycles in certain configurations.
>
> The workaround was originally introduced to improve signal reliability
> when switching cables between long and short distances. It temporarily
> forces the PHY into 10 Mbps before returning to 100 Mbps.
>
> However, when used with autonegotiating link partners (e.g., Intel i350),
> executing this workaround on every link change can confuse the partner
> and cause constant renegotiation loops. This results in repeated link
> down/up transitions and the PHY never reaching a stable state.
>
> Limit the workaround to only run during the PHY_NOLINK state. This ensures
> it is triggered only once per link drop, avoiding disruptive toggling
> while still preserving its intended effect.
>
> Note: I am not able to reproduce the original issue that this workaround
> addresses. I can only confirm that 100 Mbit mode works correctly in my
> test setup. Based on code inspection, I assume the workaround aims to
> reset some internal state machine or signal block by toggling speeds.
> However, a PHY reset is already performed earlier in the function via
> phy_init_hw(), which may achieve a similar effect. Without a reproducer,
> I conservatively keep the workaround but restrict its conditions.
>
> Fixes: e57cf3639c32 ("net: lan78xx: fix accessing the LAN7800's internal phy specific registers from the MAC driver")
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2025-07-09 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 13:07 [PATCH net v1 0/2] net: phy: microchip: LAN88xx reliability fixes Oleksij Rempel
2025-07-09 13:07 ` [PATCH net v1 1/2] net: phy: microchip: Use genphy_soft_reset() to purge stale LPA bits Oleksij Rempel
2025-07-09 14:16 ` Andrew Lunn
2025-07-09 13:07 ` [PATCH net v1 2/2] net: phy: microchip: limit 100M workaround to link-down events on LAN88xx Oleksij Rempel
2025-07-09 14:17 ` Andrew Lunn [this message]
2025-07-11 1:20 ` [PATCH net v1 0/2] net: phy: microchip: LAN88xx reliability fixes patchwork-bot+netdevbpf
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=a6c2059c-487b-4e00-9399-b98d867168b5@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=phil@raspberrypi.org \
--cc=woojung.huh@microchip.com \
--cc=yuiko.oshino@microchip.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
all inboxes | Powered by JetHome®