From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: andrew@lunn.ch, conor@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next] net: phy: vitesse: add inband caps and configuration
Date: Wed, 11 Mar 2026 14:26:11 +0000 [thread overview]
Message-ID: <abF7g9kZk5-9YN5_@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260311140135.937544-1-geert+renesas@glider.be>
On Wed, Mar 11, 2026 at 03:01:35PM +0100, Geert Uytterhoeven wrote:
> Hi Russell,
>
> On Wed, 11 Mar 2026 at 01:07, Russell King <rmk@armlinux.org.uk> wrote:
> > Add support for VSC8662 reporting its inband capabilities, and also
> > hook to configure the PHY's inband mode.
> >
> > This fixes a regression in the macb driver caused by commit
> > 1338cfef1ff1 ("net: macb: fix SGMII with inband aneg disabled")
>
> Fixes: 1338cfef1ff1b958 ("net: macb: fix SGMII with inband aneg disabled")
>
> > Reported-by: Conor Dooley <conor@kernel.org>
> > Link: https://lore.kernel.org/r/20260304-nebulizer-rounding-40fbc81a2ba1@spud
>
> s/Link/Closes/
I avoided it because any other PHY used with macb that is also connected
via SGMII will run into this same issue. It just happens that adding
this support fixes the above commit.
Conversely, we have stmmac, which unconditionally enables SGMII inband
at the MAC end no matter what phylink says to do, and should this
PHY be used with this patch in a stmmac system, it will cause that to
break, because we end up with either end misconfigured.
Also, if this commit is applied without the macb change, you'll
probably also find that macb breaks (please test that.)
So, while this is a solution and a step forward, I'd rather not suggest
that it is an official fix to the macb issue - it's merely filling in
a missing piece of the jigsaw.
Sadly, this is a fundamental issue with SGMII implementations today:
whether SGMII inband is used/required is completely random both at the
MAC/PCS end but also at the PHY end. If one ends up with a mismatch,
then things stop working.
As I say, the problem with fixing the PHY end of the link is that
it could cause a different network driver to regress.
So yes, this is a solution to the macb problem, but I regard it as
high risk.
That said, given the SGMII mess, there is no easy way forward.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2026-03-11 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 1:07 [PATCH net-next] net: phy: vitesse: add inband caps and configuration Russell King (Oracle)
2026-03-11 9:22 ` Conor Dooley
2026-03-11 14:01 ` Geert Uytterhoeven
2026-03-11 14:26 ` Russell King (Oracle) [this message]
2026-03-11 14:43 ` Geert Uytterhoeven
2026-03-11 14:54 ` Russell King (Oracle)
2026-03-11 15:04 ` Conor Dooley
2026-03-11 15:28 ` Charles Perry
2026-03-11 15:38 ` Conor Dooley
2026-03-11 14:02 ` Geert Uytterhoeven
2026-03-13 1:00 ` patchwork-bot+netdevbpf
2026-03-13 9:50 ` Conor Dooley
2026-03-14 1:59 ` Jakub Kicinski
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=abF7g9kZk5-9YN5_@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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