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 0/4] Initial support for p64h GEM
Date: Tue, 3 Mar 2026 10:03:14 -0800 [thread overview]
Message-ID: <20260303180318.1814791-1-charles.perry@microchip.com> (raw)
Hello,
This series add basic support for Microchip "PIC64-HPSC" and "PIC64HX"
(abbreviated "p64h") Ethernet endpoint. Both MPUs 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 p64h rely on
another standalone MDIO controller. For that reason, I've added a dt
binding rule to forbid phys from being added under the gem DT node. See
patch 2.
The maximum jumbo frame size also seems to be different on p64h (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 3 for more details.
p64h 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
Charles Perry (4):
dt-bindings: net: cdns,macb: add a compatible for Microchip p64h
dt-bindings: net: cdns,macb: forbid phy nodes for Microchip p64h
net: macb: add safeguards for jumbo frame larger than 10240
net: macb: add support for Microchip p64h ethernet endpoint
.../devicetree/bindings/net/cdns,macb.yaml | 12 ++++++++++++
drivers/net/ethernet/cadence/macb_main.c | 16 ++++++++++++++--
2 files changed, 26 insertions(+), 2 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-03 18:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 18:03 Charles Perry [this message]
2026-03-03 18:03 ` [PATCH net-next 1/4] dt-bindings: net: cdns,macb: add a compatible for Microchip p64h Charles Perry
2026-03-03 18:18 ` Conor Dooley
2026-03-03 18:54 ` Charles Perry
2026-03-03 19:32 ` Conor Dooley
2026-03-03 20:45 ` Charles Perry
2026-03-03 18:03 ` [PATCH net-next 2/4] dt-bindings: net: cdns,macb: forbid phy nodes " Charles Perry
2026-03-03 18:11 ` Conor Dooley
2026-03-03 18:57 ` Charles Perry
2026-03-03 18:03 ` [PATCH net-next 3/4] net: macb: add safeguards for jumbo frame larger than 10240 Charles Perry
2026-03-05 11:40 ` Simon Horman
2026-03-05 14:24 ` Charles Perry
2026-03-06 13:04 ` Simon Horman
2026-03-06 15:25 ` Charles Perry
2026-03-03 18:03 ` [PATCH net-next 4/4] net: macb: add support for Microchip p64h ethernet endpoint Charles Perry
2026-03-06 13:04 ` Simon Horman
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=20260303180318.1814791-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