From: Andrew Lunn <andrew@lunn.ch>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org,
Aleksander Jan Bajkowski <olek2@wp.pl>,
Daniel Golle <daniel@makrotopia.org>,
John Crispin <john@phrozen.org>,
Hauke Mehrtens <hauke@hauke-m.de>,
stable@vger.kernel.org
Subject: Re: [PATCH] net: phy: intel-xway: workaround 100BASE-TX Link-Up issue
Date: Tue, 15 Sep 2026 14:37:02 +0200 [thread overview]
Message-ID: <8768cdd3-e65f-4e74-9700-c21d642fa15d@lunn.ch> (raw)
In-Reply-To: <20260915085921.1354706-1-alexander.sverdlin@siemens.com>
On Tue, Sep 15, 2026 at 10:59:17AM +0200, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> MaxLinear GSW12x/GSW14x Ethernet Switch Errata Sheet states:
> "An issue has been sporadically observed after device power-on on the first
> link-up attempt in 100BASE-TX mode resulting in either the link-up taking a
> long time, or failing to link-up altogether...
>
> Workaround:
> After power-on, enable Cable Diagnostic Mode for all ports and disable
> it..."
>
> Implement the proposed workaround unconditionally in the Intel XWAY driver
> (MaxLinear GSW1xx switches incorporate Intel XWAY PHYs) because the
> diagnostic bits have the same meaning even in older integral PHYs such as
> GPY111/PEF7071/PHY11G. So it's not clear how to distinguish the affected
> newer integrated PHYs, but the workaround should not hurt the older PHYs.
>
> Cc: stable@vger.kernel.org
Please set the Subject: line correctly to indicate net, and include a
Fixes: tag.
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
Out if interest, is there sufficient details in the data sheet to
implement cable diagnostics?
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2026-09-15 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 8:59 A. Sverdlin
2026-09-15 12:37 ` Andrew Lunn [this message]
2026-09-15 12:47 ` Sverdlin, Alexander
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=8768cdd3-e65f-4e74-9700-c21d642fa15d@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexander.sverdlin@siemens.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hauke@hauke-m.de \
--cc=hkallweit1@gmail.com \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
/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®