From: Charles Perry <charles.perry@microchip.com>
To: <netdev@vger.kernel.org>
Cc: Charles Perry <charles.perry@microchip.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH net-next v3 0/3] Initial support for PIC64-HPSC/HX Ethernet endpoint
Date: Fri, 13 Mar 2026 07:06:07 -0700 [thread overview]
Message-ID: <20260313140610.3681752-1-charles.perry@microchip.com> (raw)
Hello,
This series add basic support for Microchip "PIC64-HPSC" and "PIC64HX"
Ethernet endpoint. Both SoCs contain 4 GEM IP with support for
MII/RGMII/SGMII/USXGMII at rates of 10M to 10G. Only RGMII and SGMII at a
rate of 1G is tested for now. Each GEM IP has 8 priority queues and the
revision register reads 0x220c010e.
One particularity of this instantiation of GEM is that the MDIO controller
within the GEM IP is disconnected from any physical pin and the SoC rely on
another standalone MDIO controller.
The maximum jumbo frame size also seems to be different on PIC64-HPSC/HX
(16383) than what most other platforms use (10240). I've found that I need
to tweak a bit the MTU calculation for this, otherwise the RXBS field of
the DMACFG register overflows. See patch 2 for more details.
PIC64-HPSC/HX also supports other features guarded behind CAPS bit like
MACB_CAPS_QBV but I've omitted those intentionally because I didn't test
these.
Thanks,
Charles
Changes in v3:
- Fix one more "p64h" -> "pic64hpsc"
- Remove .clk_init assignation since it's no longer required (patch 3)
Changes in v2:
- Use separate compatibles for PIC64-HPSC and PIC64HX
- "p64h" -> "pic64hpsc"
- Merge patch 2 into patch 1
Charles Perry (3):
dt-bindings: net: cdns,macb: add a compatible for Microchip pic64hpsc
net: macb: add safeguards for jumbo frame larger than 10240
net: macb: add support for Microchip pic64hpsc ethernet endpoint
.../devicetree/bindings/net/cdns,macb.yaml | 19 +++++++++++++++++++
drivers/net/ethernet/cadence/macb_main.c | 15 +++++++++++++--
2 files changed, 32 insertions(+), 2 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-13 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 14:06 Charles Perry [this message]
2026-03-13 14:06 ` [PATCH net-next v3 1/3] dt-bindings: net: cdns,macb: add a compatible for Microchip pic64hpsc Charles Perry
2026-03-17 15:31 ` Théo Lebrun
2026-03-13 14:06 ` [PATCH net-next v3 2/3] net: macb: add safeguards for jumbo frame larger than 10240 Charles Perry
2026-03-16 17:21 ` Théo Lebrun
2026-03-16 18:26 ` Charles Perry
2026-03-17 12:29 ` Paolo Abeni
2026-03-17 15:32 ` Théo Lebrun
2026-03-13 14:06 ` [PATCH net-next v3 3/3] net: macb: add support for Microchip pic64hpsc ethernet endpoint Charles Perry
2026-03-17 15:32 ` Théo Lebrun
2026-03-16 17:28 ` [PATCH net-next v3 0/3] Initial support for PIC64-HPSC/HX Ethernet endpoint Théo Lebrun
2026-03-16 18:47 ` Charles Perry
2026-03-17 12:31 ` Paolo Abeni
2026-03-17 12:40 ` 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=20260313140610.3681752-1-charles.perry@microchip.com \
--to=charles.perry@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=robh@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