From: Jonas Karlman <jonas@kwiboo.se>
To: HystericalDragons@proton.me
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Chukun Pan <amadeus@jmu.edu.cn>,
jensen <jensenhuang@friendlyarm.com>,
Andrey Korshunov <razor1702@gmail.com>,
Diederik de Haas <diederik@cknow-tech.com>
Subject: Re: [PATCH v5 2/4] arm64: dts: rockchip: Split out the common NanoPi RK3528 parts
Date: Mon, 14 Sep 2026 11:28:19 +0200 [thread overview]
Message-ID: <1074c834-1d64-4bda-b6d5-599755324dcd@kwiboo.se> (raw)
In-Reply-To: <20260914-r28s-upstream-v5-2-7409c498e8dc@proton.me>
Hi,
On 9/14/2026 10:24 AM, 安容 via B4 Relay wrote:
> From: 安容 <HystericalDragons@proton.me>
>
> The FriendlyElec NanoPi Zero2 and the NanoPi R28S share their power
> tree, storage, RGMII Ethernet, RTC, SYS LED and debug console. Move
> those parts into rk3528-nanopi.dtsi so the NanoPi R28S can reuse them,
> and leave only the board specific nodes in the NanoPi Zero2 devicetree.
>
> Suggested-by: Chukun Pan <amadeus@jmu.edu.cn>
> Signed-off-by: 安容 <HystericalDragons@proton.me>
> ---
> .../boot/dts/rockchip/rk3528-nanopi-zero2.dts | 307 +--------------------
> arch/arm64/boot/dts/rockchip/rk3528-nanopi.dtsi | 304 ++++++++++++++++++++
> 2 files changed, 313 insertions(+), 298 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3528-nanopi-zero2.dts b/arch/arm64/boot/dts/rockchip/rk3528-nanopi-zero2.dts
> index 97d85124d2..a8d99f983f 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3528-nanopi-zero2.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3528-nanopi-zero2.dts
[snip]
> -
> &usb_host0_ehci {
> status = "okay";
> };
> @@ -347,23 +74,7 @@ &usb_host0_ohci {
> status = "okay";
> };
>
> -&usb_host0_xhci {
> - extcon = <&usb2phy>;
> - maximum-speed = "high-speed";
> - phys = <&usb2phy_otg>;
> - phy-names = "usb2-phy";
> - status = "okay";
> -};
I suggest you keep all USB nodes in the device board files, NEO3 Plus
have USB 3.0 support and uses different configuration. So it will be
easier to get an overview if USB nodes are kept in the board DT.
Else most of this split matches what I played around with for U-Boot at
[1] a few weeks ago. I plan to send out the NEO3 Plus DT based on this
series later.
[1] https://git.u-boot-project.org/u-boot/contributors/kwiboo/u-boot/-/commit/40382468ba7ce9aa2e7dcde0e59003fd0d220b43
Regards,
Jonas
> -
> -&usb2phy {
> - status = "okay";
> -};
> -
> &usb2phy_host {
> phy-supply = <&usb2_host_5v>;
> status = "okay";
> };
> -
> -&usb2phy_otg {
> - status = "okay";
> -};
[snip]
next prev parent reply other threads:[~2026-09-14 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:24 [PATCH v5 0/4] arm64: dts: rockchip: Add FriendlyElec NanoPi R28S 安容 via B4 Relay
2026-09-14 8:24 ` [PATCH v5 1/4] dt-bindings: arm: " 安容 via B4 Relay
2026-09-14 9:13 ` Jonas Karlman
2026-09-14 8:24 ` [PATCH v5 2/4] arm64: dts: rockchip: Split out the common NanoPi RK3528 parts 安容 via B4 Relay
2026-09-14 9:28 ` Jonas Karlman [this message]
2026-09-14 8:24 ` [PATCH v5 3/4] arm64: dts: rockchip: Add devicetree for the FriendlyElec NanoPi R28S 安容 via B4 Relay
2026-09-14 9:46 ` Jonas Karlman
2026-09-14 13:37 ` 安容
2026-09-14 8:24 ` [PATCH v5 4/4] arm64: dts: rockchip: Follow the DTS coding style in the NanoPi RK3528 devicetrees 安容 via B4 Relay
2026-09-14 8:58 ` [PATCH v5 0/4] arm64: dts: rockchip: Add FriendlyElec NanoPi R28S Diederik de Haas
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=1074c834-1d64-4bda-b6d5-599755324dcd@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=HystericalDragons@proton.me \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--cc=heiko@sntech.de \
--cc=jensenhuang@friendlyarm.com \
--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=razor1702@gmail.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
all inboxes | Powered by JetHome®