From: Coia Prant <coiaprant@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Lin <shawn.lin@rock-chips.com>,
David Heidelberg <david@ixit.cz>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Coia Prant <coiaprant@gmail.com>
Subject: [PATCH v11 0/3] arm64: dts: rockchip: add RK3568 XPCS nodes and enable SGMII on Photonicat
Date: Thu, 22 Oct 2026 10:58:41 +0800 [thread overview]
Message-ID: <20261022025844.150320-1-coiaprant@gmail.com> (raw)
This series adds the RK3568 XPCS and fixed-clock nodes, describes the
RGMII PHY LEDs on the Ariaboard Photonicat, and enables the SGMII LAN
port on the same board.
Changes since v10:
- The rockchip,sgmii-mac-sel property on combphy2 is no longer set in
the Photonicat DTS. The property is tri-state: when absent, the
driver leaves the routing unchanged. If the bootloader has already
routed combphy2 SGMII to GMAC0, the link works without the explicit
property. A follow-up will add it once the PHY binding lands in
linux-next.
- The RGMII PHY LED configuration is now a separate patch (patch 2).
- The SGMII PHY LED configuration on mdio0 stays in the Photonicat
patch (patch 3), since it belongs to the port being enabled.
Dependencies:
- XPCS binding and driver (rockchip,rk3568-xpcs, XPCS glue, dwmac-rk
SGMII, pcs-handle binding): merged in net-next and present in
linux-next.
https://git.kernel.org/netdev/net-next/c/5e91edfb0e45
- PHY binding+driver (rockchip,sgmii-mac-sel): still in review on
linux-phy. Not required for this version to compile or pass
dtbs_check; only needed for the follow-up that sets the property
explicitly.
- Generic PM domain (genpd) changes: runtime-only, not a DTS
dependency.
The XPCS node is disabled by default and only enabled on boards that
use SGMII. The fixed-clock nodes are always present, as they are
static clock sources.
dtbs_check passes with the current linux-next, since the XPCS binding
is already merged.
---
Coia Prant (3):
arm64: dts: rockchip: rk3568: add XPCS and fixed-clock nodes
arm64: dts: rockchip: rk3568-photonicat: add RGMII PHY LEDs
arm64: dts: rockchip: rk3568-photonicat: enable SGMII LAN port
.../boot/dts/rockchip/rk3568-photonicat.dts | 68 ++++++++++++++++++-
arch/arm64/boot/dts/rockchip/rk3568.dtsi | 23 +++++++
2 files changed, 89 insertions(+), 2 deletions(-)
--
2.47.3
next reply other threads:[~2026-10-22 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 2:58 Coia Prant [this message]
2026-10-22 2:58 ` [PATCH v11 1/3] arm64: dts: rockchip: rk3568: add XPCS and fixed-clock nodes Coia Prant
2026-10-22 2:58 ` [PATCH v11 2/3] arm64: dts: rockchip: rk3568-photonicat: add RGMII PHY LEDs Coia Prant
2026-10-22 2:58 ` [PATCH v11 3/3] arm64: dts: rockchip: rk3568-photonicat: enable SGMII LAN port Coia Prant
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=20261022025844.150320-1-coiaprant@gmail.com \
--to=coiaprant@gmail.com \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.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
all inboxes | Powered by JetHome®