From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
Mohd Ayaan Anwar <mohd.anwar@oss.qualcomm.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Vinod Koul <vkoul@kernel.org>
Subject: [PATCH net-next v2 maybe? 0/5] net: stmmac: improve PCS support
Date: Wed, 18 Mar 2026 16:05:53 +0000 [thread overview]
Message-ID: <abrNYVfZ1Iwff2EI@shell.armlinux.org.uk> (raw)
I am losing track of what version we're at, because each time the
series is reworked, changing the approach, which changes the
patches quite a bit, it makes it difficult. We've gone RFC to non-RFC
back to RFC and then to non-RFC again.
This series is the next of the three part series sorting out the PCS
support in stmmac, building on part 2:
net: stmmac: qcom-ethqos: further serdes reorganisation
Similar patches have been posted previously. This series does away with
the common SerDes PHY support, instead using a flag to indicate whether
2500Mbps mode is supported (STMMAC_FLAG_SERDES_SUPPORTS_2500M.) At this
time, I have no plans to resurect the common SerDes PHY support - the
generic PHY layer implementations are just too random to consider that,
and I certainly do not want the extra work of fixing that.
Changes from RFC v3:
- only set default_an_inband if using SGMII/2500BASE-X mode.
Changes from previous non-RFC posting:
- add a patch moving default_an_inband to struct plat_stmmacenet_data
- only include the first four patches from the previous posting
- add pcs_an_restart() support for BASE-X, but only if we have
TBI/RTBI support.
The reasoning here is that these patches should be safe to merge and
should not impact qcom-ethqos in any way.
We can then figure out how to work around qcom-ethqos hacks without
having to keep re-posting these same patches time and time again.
drivers/net/ethernet/stmicro/stmmac/common.h | 4 -
drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c | 4 +-
drivers/net/ethernet/stmicro/stmmac/dwmac1000.h | 12 +-
.../net/ethernet/stmicro/stmmac/dwmac1000_core.c | 11 +-
drivers/net/ethernet/stmicro/stmmac/dwmac4.h | 10 +-
drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c | 10 +-
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 13 +-
drivers/net/ethernet/stmicro/stmmac/stmmac_pcs.c | 156 ++++++++++++++++++++-
drivers/net/ethernet/stmicro/stmmac/stmmac_pcs.h | 14 +-
include/linux/stmmac.h | 3 +-
10 files changed, 186 insertions(+), 51 deletions(-)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next reply other threads:[~2026-03-18 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 16:05 Russell King (Oracle) [this message]
2026-03-18 16:06 ` [PATCH net-next v2 maybe? 1/5] net: stmmac: move default_an_inband to plat_stmmacenet_data Russell King (Oracle)
2026-03-18 16:06 ` [PATCH net-next v2 maybe? 2/5] net: stmmac: add struct stmmac_pcs_info Russell King (Oracle)
2026-03-18 16:06 ` [PATCH net-next v2 maybe? 3/5] net: stmmac: add support for reading inband SGMII status Russell King (Oracle)
2026-03-18 16:06 ` [PATCH net-next v2 maybe? 4/5] net: stmmac: add BASE-X support to integrated PCS Russell King (Oracle)
2026-03-18 16:06 ` [PATCH net-next v2 maybe? 5/5] net: stmmac: use integrated PCS for BASE-X modes Russell King (Oracle)
2026-03-24 0:40 ` [PATCH net-next v2 maybe? 0/5] net: stmmac: improve PCS support 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=abrNYVfZ1Iwff2EI@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mohd.anwar@oss.qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.