From: Jonas Karlman <jonas@kwiboo.se>
To: Heiko Stuebner <heiko@sntech.de>,
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>
Cc: Yao Zi <ziyao@disroot.org>,
linux-rockchip@lists.infradead.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jonas Karlman <jonas@kwiboo.se>
Subject: [PATCH 0/4] rockchip: Enable Ethernet controller on Radxa E20C
Date: Thu, 6 Mar 2025 22:13:53 +0000 [thread overview]
Message-ID: <20250306221402.1704196-1-jonas@kwiboo.se> (raw)
The Rockchip RK3528 has two Ethernet controllers, one 100/10 MAC to be
used with the integrated PHY and a second 1000/100/10 MAC to be used
with an external Ethernet PHY.
This series add initial support for the Ethernet controllers found in
RK3528 and enable the LAN interface on Radxa E20C.
This only add a bare minimum gmac0 node for the 100/10 MAC and skip e.g.
parts to power on and off the integrated PHY in GMAC driver becayse I do
not have any RK3528 device that make use of gmac0.
This series depends on the "net: stmmac: dwmac-rk: Validate rockchip,grf
and php-grf during probe" cleanup series to ensure bsp_priv->grf can be
used. And possible also on the leds+buttons, sdio+sdmmc and sdhci series
for RK3528 for a clean apply.
David Wu (1):
ethernet: stmmac: dwmac-rk: Add GMAC support for RK3528
Jonas Karlman (3):
dt-bindings: net: rockchip-dwmac: Add compatible string for RK3528
arm64: dts: rockchip: Add GMAC nodes for RK3528
arm64: dts: rockchip: Enable Ethernet controller on Radxa E20C
.../bindings/net/rockchip-dwmac.yaml | 4 +-
.../boot/dts/rockchip/rk3528-radxa-e20c.dts | 30 ++++
arch/arm64/boot/dts/rockchip/rk3528.dtsi | 92 ++++++++++++
.../net/ethernet/stmicro/stmmac/dwmac-rk.c | 132 ++++++++++++++++++
4 files changed, 257 insertions(+), 1 deletion(-)
--
2.48.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2025-03-06 22:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 22:13 Jonas Karlman [this message]
2025-03-06 22:13 ` [PATCH 1/4] dt-bindings: net: rockchip-dwmac: Add compatible string for RK3528 Jonas Karlman
2025-03-07 15:42 ` Conor Dooley
2025-03-07 16:01 ` Jonas Karlman
2025-03-06 22:13 ` [PATCH 2/4] ethernet: stmmac: dwmac-rk: Add GMAC support " Jonas Karlman
2025-03-06 22:13 ` [PATCH 3/4] arm64: dts: rockchip: Add GMAC nodes " Jonas Karlman
2025-03-06 22:46 ` Andrew Lunn
2025-03-07 0:05 ` Jonas Karlman
2025-03-07 14:02 ` Andrew Lunn
2025-03-06 22:13 ` [PATCH 4/4] arm64: dts: rockchip: Enable Ethernet controller on Radxa E20C Jonas Karlman
2025-03-06 22:49 ` Andrew Lunn
2025-03-07 9:16 ` Jonas Karlman
2025-03-07 13:25 ` Andrew Lunn
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=20250306221402.1704196-1-jonas@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=ziyao@disroot.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