From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andre Edich <andre.edich@microchip.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH net v2 2/3] net: phy: smsc: Force predictable MDI-X state on LAN87xx
Date: Fri, 4 Jul 2025 10:00:31 +0200 [thread overview]
Message-ID: <20250704100031.19f95d3e@fedora.home> (raw)
In-Reply-To: <20250703114941.3243890-3-o.rempel@pengutronix.de>
On Thu, 3 Jul 2025 13:49:40 +0200
Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> Override the hardware strap configuration for MDI-X mode to ensure a
> predictable initial state for the driver. The initial mode of the LAN87xx
> PHY is determined by the AUTOMDIX_EN strap pin, but the driver has no
> documented way to read its latched status.
>
> This unpredictability means the driver cannot know if the PHY has
> initialized with Auto-MDIX enabled or disabled, preventing it from
> providing a reliable interface to the user.
>
> This patch introduces a `config_init` hook that forces the PHY into a
> known state by explicitly enabling Auto-MDIX.
>
> Fixes: 05b35e7eb9a1 ("smsc95xx: add phylib support")
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> Cc: Andre Edich <andre.edich@microchip.com>
The patch looks good to me, but I have a few questions. As this
overrides some configuration on existing HW, and I'm not utra familiar
with auto-mdix, is there any chance this could cause regressions ?
Especially regarding your patch 3, is there any chance that the PHY is
strapped in a fixed MDIX mode to address the broken autoneg off mode ?
I'm not saying that strapping is a good solution for that ofc :) it's a
shame we can't read the strap config :/
Maxime
next prev parent reply other threads:[~2025-07-04 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 11:49 [PATCH net v2 0/4] net: phy: smsc: robustness fixes for LAN87xx/LAN9500 Oleksij Rempel
2025-07-03 11:49 ` [PATCH net v2 1/3] net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap Oleksij Rempel
2025-07-04 7:53 ` Maxime Chevallier
2025-07-03 11:49 ` [PATCH net v2 2/3] net: phy: smsc: Force predictable MDI-X state on LAN87xx Oleksij Rempel
2025-07-04 8:00 ` Maxime Chevallier [this message]
2025-07-04 8:16 ` Andrew Lunn
2025-07-03 11:49 ` [PATCH net v2 3/3] net: phy: smsc: Fix link failure in forced mode with Auto-MDIX Oleksij Rempel
2025-07-04 8:23 ` Andrew Lunn
2025-07-09 1:30 ` [PATCH net v2 0/4] net: phy: smsc: robustness fixes for LAN87xx/LAN9500 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=20250704100031.19f95d3e@fedora.home \
--to=maxime.chevallier@bootlin.com \
--cc=andre.edich@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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®