From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: "Heiko Stuebner" <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
"Martin Holovský (Probably Nothing s.r.o.)" <mh@probably.group>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: enable both 2.5GbE ports on Rock 5T
Date: Fri, 19 Dec 2025 14:06:12 +0100 [thread overview]
Message-ID: <3903009.mvXUDI8C0e@workhorse> (raw)
In-Reply-To: <034BDB37-34FB-441F-B79E-1631CA501576@probably.group>
On Thursday, 18 December 2025 07:27:06 Central European Standard Time Martin Holovský (Probably Nothing s.r.o.) wrote:
> The Radxa Rock 5T board features two RTL8125B 2.5GbE Ethernet controllers
> connected via PCIe lanes pcie2x1l0 (fe170000) and pcie2x1l2 (fe190000).
> Currently only one interface is functional because the PCIe controller
> nodes lack the necessary reset GPIO configuration.
>
> Without the reset-gpios property, the RTL8125B PHYs remain in reset state
> and are not enumerated by the PCIe bus. This results in only one Ethernet
> interface being detected, or none at all depending on U-Boot initialization.
>
> This patch adds the missing configuration for both PCIe controllers:
> - Enables both pcie2x1l0 and pcie2x1l2 nodes (status = "okay")
> - Configures reset GPIOs (GPIO4_PA5 and GPIO3_PB0 respectively)
> - Adds corresponding pinctrl definitions
>
> With this change, both 2.5GbE interfaces are properly detected and
> functional on the Rock 5T.
>
> Tested on Radxa Rock 5T v1.2 running Linux 6.12.
>
> Signed-off-by: Martin Holovsky <mh@probably.group>
> ---
> Changes in v2:
> - Sorted pcie nodes alphanumerically
> - Sorted pinctrl nodes alphanumerically
> - Added Signed-off-by line
>
> .../boot/dts/rockchip/rk3588-rock-5t.dts | 28 +++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-rock-5t.dts b/arch/arm64/boot/dts/rockchip/rk3588-rock-5t.dts
> index 0dd90c744380..aeb8e0d42f09 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-rock-5t.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-rock-5t.dts
> @@ -68,10 +68,24 @@ &pcie2x1l1 {
> reset-gpios = <&gpio4 RK_PA2 GPIO_ACTIVE_HIGH>;
> status = "okay";
> };
>
> +&pcie2x1l0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pcie2_0_rst>;
> + reset-gpios = <&gpio4 RK_PA5 GPIO_ACTIVE_HIGH>;
> + status = "okay";
> +};
> +
> +&pcie2x1l2 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pcie2_2_rst>;
> + reset-gpios = <&gpio3 RK_PB0 GPIO_ACTIVE_HIGH>;
> + status = "okay";
> +};
> +
> &pcie30phy {
> data-lanes = <1 1 2 2>;
> };
> @@ -101,6 +115,14 @@ pcie2 {
> + pcie2_0_rst: pcie2-0-rst {
> + rockchip,pins = <4 RK_PA5 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> pcie2_1_rst: pcie2-1-rst {
> rockchip,pins = <4 RK_PA2 RK_FUNC_GPIO &pcfg_pull_none>;
> };
> +
> + pcie2_2_rst: pcie2-2-rst {
> + rockchip,pins = <3 RK_PB0 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> pcie2_0_vcc3v3_en: pcie2-0-vcc-en {
> rockchip,pins = <2 RK_PC0 RK_FUNC_GPIO &pcfg_pull_none>;
> };
>
This stuff is already in rk3588-rock-5b-5bp-5t.dtsi. Ergo, this patch
does nothing at all. What are you actually trying to solve?
Heiko, please don't apply this.
Kind regards,
Nicolas Frattaroli
next prev parent reply other threads:[~2025-12-19 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 16:23 [PATCH] arm64: dts: rockchip: enable dual 2.5GbE on Rock 5T "Martin Holovský (Probably Nothing s.r.o.)"
2025-12-15 13:51 ` Heiko Stuebner
2025-12-15 21:47 ` Heiko Stübner
2025-12-17 23:31 ` "Martin Holovský (Probably Nothing s.r.o.)"
2025-12-18 6:27 ` [PATCH v2] arm64: dts: rockchip: enable both 2.5GbE ports " "Martin Holovský (Probably Nothing s.r.o.)"
2025-12-19 13:05 ` FUKAUMI Naoki
2025-12-19 13:06 ` Nicolas Frattaroli [this message]
2025-12-22 12:18 ` Heiko Stuebner
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=3903009.mvXUDI8C0e@workhorse \
--to=nicolas.frattaroli@collabora.com \
--cc=conor+dt@kernel.org \
--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=mh@probably.group \
--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;
as well as URLs for NNTP newsgroup(s).