From: Mieczyslaw Nalewaj <namiltd@yahoo.com>
To: Johan Alvarado <contact@c127.dev>,
linusw@kernel.org, alsi@bang-olufsen.dk, andrew@lunn.ch,
olteanv@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, linux@armlinux.org.uk
Cc: luizluca@gmail.com, maxime.chevallier@bootlin.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 2/2] net: dsa: realtek: rtl8365mb: add HSGMII support for RTL8367S
Date: Fri, 3 Jul 2026 17:12:40 +0200 [thread overview]
Message-ID: <577055ac-9378-4d43-9ff2-1a1dd17ae9dc@yahoo.com> (raw)
In-Reply-To: <0100019f24962e49-10163ad6-22fd-4528-b8f3-75703cfd80dc-000000@email.amazonses.com>
On 7/2/2026 10:47 PM, Johan Alvarado wrote:
> In addition to SGMII, the RTL8367S SerDes also supports HSGMII, which
> carries 2.5 Gbps with the same signaling as SGMII at 2.5x clock rate.
> The chip info table already declares HSGMII as a supported interface
> mode for external interface 1.
>
> Extend the SerDes PCS to handle HSGMII, which phylink represents as
> 2500base-x:
>
> - Select the HSGMII SerDes tuning parameters and external interface
> mode, and mux the SerDes to MAC8 in HSGMII mode, from pcs_config()
> according to the interface. The parameters are again lifted from the
> GPL-licensed Realtek rtl8367c vendor driver, and again only cover
> the tuning variant for a non-zero chip option, so the mode is gated
> on the option probed at setup.
[...]
> @@ -1264,6 +1279,16 @@ static int rtl8365mb_pcs_config(struct phylink_pcs *pcs, unsigned int neg_mode,
> if (neg_mode == PHYLINK_PCS_NEG_INBAND_ENABLED)
> return -EOPNOTSUPP;
>
> + if (interface == PHY_INTERFACE_MODE_2500BASEX) {
> + sds_jam = rtl8365mb_sds_jam_hsgmii;
> + sds_jam_size = ARRAY_SIZE(rtl8365mb_sds_jam_hsgmii);
> + mode = RTL8365MB_EXT_PORT_MODE_HSGMII;
> + } else {
> + sds_jam = rtl8365mb_sds_jam_sgmii;
> + sds_jam_size = ARRAY_SIZE(rtl8365mb_sds_jam_sgmii);
> + mode = RTL8365MB_EXT_PORT_MODE_SGMII;
> + }
> +
Johan, looks like you forgot to include the scheduler bandwidth bits for the CPU port. Without this, HSGMII will still be capped at the old SGMII rate limits. Something like:
#define RTL8365MB_REG_INGRESSBW_PORT6_RATE_CTRL1 0x00d0
#define RTL8365MB_INGRESSBW_PORT6_RATE_CTRL1_INGRESSBW_RATE16_MASK GENMASK(2, 0)
#define RTL8365MB_REG_PORT6_EGRESSBW_CTRL1 0x0399
#define RTL8365MB_PORT6_EGRESSBW_CTRL1_MASK GENMASK(2, 0)
#define RTL8365MB_REG_LINE_RATE_HSG_H 0x03fa
#define RTL8365MB_LINE_RATE_HSG_H_MASK GENMASK(2, 0)
[...]
/* Allow full 2.5G on HSGMII CPU port: set scheduler
* bandwidth limits to max (0x7). Fixed-link init-only;
* no runtime SGMII reconfiguration is expected here.
*/
ret = regmap_write(priv->map,
RTL8365MB_REG_INGRESSBW_PORT6_RATE_CTRL1,
FIELD_PREP(RTL8365MB_INGRESSBW_PORT6_RATE_CTRL1_INGRESSBW_RATE16_MASK,
7));
if (ret)
return ret;
ret = regmap_write(priv->map,
RTL8365MB_REG_PORT6_EGRESSBW_CTRL1,
FIELD_PREP(RTL8365MB_PORT6_EGRESSBW_CTRL1_MASK,
7));
if (ret)
return ret;
ret = regmap_write(priv->map,
RTL8365MB_REG_LINE_RATE_HSG_H,
FIELD_PREP(RTL8365MB_LINE_RATE_HSG_H_MASK,
7));
if (ret)
return ret;
One more thing while we're on this: I checked the equivalent registers for RGMII on the RTL8367S, and they come out to 1, 1, 7 respectively (INGRESSBW_PORT6_RATE_CTRL1, PORT6_EGRESSBW_CTRL1, LINE_RATE_HSG_H). For correctness these should be set to those values in the RGMII path as well, rather than left at whatever reset/default state they're currently in.
prev parent reply other threads:[~2026-07-03 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260702204648.276112-1-contact@c127.dev>
2026-07-02 20:47 ` [PATCH net-next v4 1/2] net: dsa: realtek: rtl8365mb: add SGMII support for RTL8367S Johan Alvarado
2026-07-03 7:29 ` Maxime Chevallier
2026-07-02 20:47 ` [PATCH net-next v4 2/2] net: dsa: realtek: rtl8365mb: add HSGMII " Johan Alvarado
2026-07-03 15:12 ` Mieczyslaw Nalewaj [this message]
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=577055ac-9378-4d43-9ff2-1a1dd17ae9dc@yahoo.com \
--to=namiltd@yahoo.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=contact@c127.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luizluca@gmail.com \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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