[PATCH net-next] net: pcs: lynx: accept in-band autoneg for 2500base-x

[PATCH net-next] net: pcs: lynx: accept in-band autoneg for 2500base-x

[Vladimir Oltean]

Testing in two circumstances:

1. back to back optical SFP+ connection between two LS1028A-QDS ports
   with the SCH-26908 riser card
2. T1042 with on-board AQR115 PHY using "OCSGMII", as per
   https://lore.kernel.org/lkml/aIuEvaSCIQdJWcZx@FUE-ALEWI-WINX/

strongly suggests that enabling in-band auto-negotiation is actually
possible when the lane baud rate is 3.125 Gbps.

It was previously thought that this would not be the case, because it
was only tested on 2500base-x links with on-board Aquantia PHYs, where
it was noticed that MII_LPA is always reported as zero, and it was
thought that this is because of the PCS.

Test case #1 above shows it is not, and the configured MII_ADVERTISE on
system A ends up in the MII_LPA on system B, when in 2500base-x mode
(IF_MODE=0).

Test case #2, which uses "SGMII" auto-negotiation (IF_MODE=3) for the
3.125 Gbps lane, is actually a misconfiguration, but it is what led to
the discovery.

There is actually an old bug in the Lynx PCS driver - it expects all
register values to contain their default out-of-reset values, as if the
PCS were initialized by the Reset Configuration Word (RCW) settings.
There are 2 cases in which this is problematic:
- if the bootloader (or previous kexec-enabled Linux) wrote a different
  IF_MODE value
- if dynamically changing the SerDes protocol from 1000base-x to
  2500base-x, e.g. by replacing the optical SFP module.

Specifically in test case #2, an accidental alignment between the
bootloader configuring the PCS to expect SGMII in-band code words, and
the AQR115 PHY actually transmitting SGMII in-band code words when
operating in the "OCSGMII" system interface protocol, led to the PCS
transmitting replicated symbols at 3.125 Gbps baud rate. This could only
have happened if the PCS saw and reacted to the SGMII code words in the
first place.

Since test #2 is invalid from a protocol perspective (there seems to be
no standard way of negotiating the data rate of 2500 Mbps with SGMII,
and the lower data rates should remain 10/100/1000), in-band auto-negotiation
for 2500base-x effectively means Clause 37 (i.e. IF_MODE=0).

Make 2500base-x be treated like 1000base-x in this regard, by removing
all prior limitations and calling lynx_pcs_config_giga().

This adds a new feature: LINK_INBAND_ENABLE and at the same time fixes
the Lynx PCS's long standing problem that the registers (specifically
IF_MODE, but others could be misconfigured as well) are not written by
the driver to the known valid values for 2500base-x.

Co-developed-by: Alexander Wilhelm <alexander.wilhelm@westermo.com>
Signed-off-by: Alexander Wilhelm <alexander.wilhelm@westermo.com>
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
 drivers/net/pcs/pcs-lynx.c | 13 ++++---------
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/drivers/net/pcs/pcs-lynx.c b/drivers/net/pcs/pcs-lynx.c
index 677f92883976..a88cbe67cc9d 100644
--- a/drivers/net/pcs/pcs-lynx.c
+++ b/drivers/net/pcs/pcs-lynx.c
@@ -40,12 +40,12 @@ static unsigned int lynx_pcs_inband_caps(struct phylink_pcs *pcs,
 {
 	switch (interface) {
 	case PHY_INTERFACE_MODE_1000BASEX:
+	case PHY_INTERFACE_MODE_2500BASEX:
 	case PHY_INTERFACE_MODE_SGMII:
 	case PHY_INTERFACE_MODE_QSGMII:
 		return LINK_INBAND_DISABLE | LINK_INBAND_ENABLE;
 
 	case PHY_INTERFACE_MODE_10GBASER:
-	case PHY_INTERFACE_MODE_2500BASEX:
 		return LINK_INBAND_DISABLE;
 
 	case PHY_INTERFACE_MODE_USXGMII:
@@ -152,7 +152,8 @@ static int lynx_pcs_config_giga(struct mdio_device *pcs,
 		mdiodev_write(pcs, LINK_TIMER_HI, link_timer >> 16);
 	}
 
-	if (interface == PHY_INTERFACE_MODE_1000BASEX) {
+	if (interface == PHY_INTERFACE_MODE_1000BASEX ||
+	    interface == PHY_INTERFACE_MODE_2500BASEX) {
 		if_mode = 0;
 	} else {
 		/* SGMII and QSGMII */
@@ -202,15 +203,9 @@ static int lynx_pcs_config(struct phylink_pcs *pcs, unsigned int neg_mode,
 	case PHY_INTERFACE_MODE_1000BASEX:
 	case PHY_INTERFACE_MODE_SGMII:
 	case PHY_INTERFACE_MODE_QSGMII:
+	case PHY_INTERFACE_MODE_2500BASEX:
 		return lynx_pcs_config_giga(lynx->mdio, ifmode, advertising,
 					    neg_mode);
-	case PHY_INTERFACE_MODE_2500BASEX:
-		if (neg_mode == PHYLINK_PCS_NEG_INBAND_ENABLED) {
-			dev_err(&lynx->mdio->dev,
-				"AN not supported on 3.125GHz SerDes lane\n");
-			return -EOPNOTSUPP;
-		}
-		break;
 	case PHY_INTERFACE_MODE_USXGMII:
 	case PHY_INTERFACE_MODE_10G_QXGMII:
 		return lynx_pcs_config_usxgmii(lynx->mdio, ifmode, advertising,
-- 
2.34.1

Re: [PATCH net-next] net: pcs: lynx: accept in-band autoneg for 2500base-x

[Russell King (Oracle)]

On Sat, Nov 22, 2025 at 01:34:33PM +0200, Vladimir Oltean wrote:
> Testing in two circumstances:
> 
> 1. back to back optical SFP+ connection between two LS1028A-QDS ports
>    with the SCH-26908 riser card
> 2. T1042 with on-board AQR115 PHY using "OCSGMII", as per
>    https://lore.kernel.org/lkml/aIuEvaSCIQdJWcZx@FUE-ALEWI-WINX/
> 
> strongly suggests that enabling in-band auto-negotiation is actually
> possible when the lane baud rate is 3.125 Gbps.
> 
> It was previously thought that this would not be the case, because it
> was only tested on 2500base-x links with on-board Aquantia PHYs, where
> it was noticed that MII_LPA is always reported as zero, and it was
> thought that this is because of the PCS.

Yay. 

> 
> Test case #1 above shows it is not, and the configured MII_ADVERTISE on
> system A ends up in the MII_LPA on system B, when in 2500base-x mode
> (IF_MODE=0).
> 
> Test case #2, which uses "SGMII" auto-negotiation (IF_MODE=3) for the
> 3.125 Gbps lane, is actually a misconfiguration, but it is what led to
> the discovery.
> 
> There is actually an old bug in the Lynx PCS driver - it expects all
> register values to contain their default out-of-reset values, as if the
> PCS were initialized by the Reset Configuration Word (RCW) settings.
> There are 2 cases in which this is problematic:
> - if the bootloader (or previous kexec-enabled Linux) wrote a different
>   IF_MODE value
> - if dynamically changing the SerDes protocol from 1000base-x to
>   2500base-x, e.g. by replacing the optical SFP module.
> 
> Specifically in test case #2, an accidental alignment between the
> bootloader configuring the PCS to expect SGMII in-band code words, and
> the AQR115 PHY actually transmitting SGMII in-band code words when
> operating in the "OCSGMII" system interface protocol, led to the PCS
> transmitting replicated symbols at 3.125 Gbps baud rate. This could only
> have happened if the PCS saw and reacted to the SGMII code words in the
> first place.
> 
> Since test #2 is invalid from a protocol perspective (there seems to be
> no standard way of negotiating the data rate of 2500 Mbps with SGMII,
> and the lower data rates should remain 10/100/1000), in-band auto-negotiation
> for 2500base-x effectively means Clause 37 (i.e. IF_MODE=0).
> 
> Make 2500base-x be treated like 1000base-x in this regard, by removing
> all prior limitations and calling lynx_pcs_config_giga().
> 
> This adds a new feature: LINK_INBAND_ENABLE and at the same time fixes
> the Lynx PCS's long standing problem that the registers (specifically
> IF_MODE, but others could be misconfigured as well) are not written by
> the driver to the known valid values for 2500base-x.
> 
> Co-developed-by: Alexander Wilhelm <alexander.wilhelm@westermo.com>
> Signed-off-by: Alexander Wilhelm <alexander.wilhelm@westermo.com>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>

This looks to be incomplete - if AN is now supported at 2500base-X,
lynx_pcs_get_state_2500basex() is obsolete. As with 1000base-X,
phylink_mii_c22_pcs_get_state() can be called to retrieve the state
and it will do the right thing wrt 2.5G speeds.

Next, please look at whether lynx_pcs_link_up_2500basex() is necessary,
and whether the speed and duplex modes need to also be programmed for
1000base-X when inband is not enabled.

Essentially, by saying that inband is supported at 2.5G speeds as well
as 1G, both 1000base-X and 2500base-X should be treated the same way
by the PCS driver, so the code paths should be the same.

I note that SGMII_SPEED_2500 == SGMII_SPEED_1000, which means the
IF_MODE programming as far as HD+speed should end up being the same
for both these interface modes.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

Re: [PATCH net-next] net: pcs: lynx: accept in-band autoneg for 2500base-x

[Vladimir Oltean]

On Sat, Nov 22, 2025 at 11:58:00AM +0000, Russell King (Oracle) wrote:
> On Sat, Nov 22, 2025 at 01:34:33PM +0200, Vladimir Oltean wrote:
> > Testing in two circumstances:
> > 
> > 1. back to back optical SFP+ connection between two LS1028A-QDS ports
> >    with the SCH-26908 riser card
> > 2. T1042 with on-board AQR115 PHY using "OCSGMII", as per
> >    https://lore.kernel.org/lkml/aIuEvaSCIQdJWcZx@FUE-ALEWI-WINX/
> > 
> > strongly suggests that enabling in-band auto-negotiation is actually
> > possible when the lane baud rate is 3.125 Gbps.
> > 
> > It was previously thought that this would not be the case, because it
> > was only tested on 2500base-x links with on-board Aquantia PHYs, where
> > it was noticed that MII_LPA is always reported as zero, and it was
> > thought that this is because of the PCS.
> 
> Yay. 

Yay indeed...

> > Test case #1 above shows it is not, and the configured MII_ADVERTISE on
> > system A ends up in the MII_LPA on system B, when in 2500base-x mode
> > (IF_MODE=0).
> > 
> > Test case #2, which uses "SGMII" auto-negotiation (IF_MODE=3) for the
> > 3.125 Gbps lane, is actually a misconfiguration, but it is what led to
> > the discovery.
> > 
> > There is actually an old bug in the Lynx PCS driver - it expects all
> > register values to contain their default out-of-reset values, as if the
> > PCS were initialized by the Reset Configuration Word (RCW) settings.
> > There are 2 cases in which this is problematic:
> > - if the bootloader (or previous kexec-enabled Linux) wrote a different
> >   IF_MODE value
> > - if dynamically changing the SerDes protocol from 1000base-x to
> >   2500base-x, e.g. by replacing the optical SFP module.
> > 
> > Specifically in test case #2, an accidental alignment between the
> > bootloader configuring the PCS to expect SGMII in-band code words, and
> > the AQR115 PHY actually transmitting SGMII in-band code words when
> > operating in the "OCSGMII" system interface protocol, led to the PCS
> > transmitting replicated symbols at 3.125 Gbps baud rate. This could only
> > have happened if the PCS saw and reacted to the SGMII code words in the
> > first place.
> > 
> > Since test #2 is invalid from a protocol perspective (there seems to be
> > no standard way of negotiating the data rate of 2500 Mbps with SGMII,
> > and the lower data rates should remain 10/100/1000), in-band auto-negotiation
> > for 2500base-x effectively means Clause 37 (i.e. IF_MODE=0).
> > 
> > Make 2500base-x be treated like 1000base-x in this regard, by removing
> > all prior limitations and calling lynx_pcs_config_giga().
> > 
> > This adds a new feature: LINK_INBAND_ENABLE and at the same time fixes
> > the Lynx PCS's long standing problem that the registers (specifically
> > IF_MODE, but others could be misconfigured as well) are not written by
> > the driver to the known valid values for 2500base-x.
> > 
> > Co-developed-by: Alexander Wilhelm <alexander.wilhelm@westermo.com>
> > Signed-off-by: Alexander Wilhelm <alexander.wilhelm@westermo.com>
> > Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> 
> This looks to be incomplete - if AN is now supported at 2500base-X,
> lynx_pcs_get_state_2500basex() is obsolete. As with 1000base-X,
> phylink_mii_c22_pcs_get_state() can be called to retrieve the state
> and it will do the right thing wrt 2.5G speeds.
> 
> Next, please look at whether lynx_pcs_link_up_2500basex() is necessary,
> and whether the speed and duplex modes need to also be programmed for
> 1000base-X when inband is not enabled.
> 
> Essentially, by saying that inband is supported at 2.5G speeds as well
> as 1G, both 1000base-X and 2500base-X should be treated the same way
> by the PCS driver, so the code paths should be the same.

Thanks for the feedback. I can't easily tell if these fixups were later
made in the thread with Alexander or not, because it's hard to fish
useful things for submission from an old debugging thread. I'll make
these changes and retest on my LS1028A-QDS rig from the lab.

> I note that SGMII_SPEED_2500 == SGMII_SPEED_1000, which means the
> IF_MODE programming as far as HD+speed should end up being the same
> for both these interface modes.

Yeah, it would make sense for the configuration as well as code paths to
be fully identical for these 2 BASE-X modes.