From: Chen-Yu Tsai <wens@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Chen-Yu Tsai <wens@kernel.org>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH] arm64: dts: rockchip: rk3399-nanopi-r4s: Disable removed devices
Date: Wed, 6 May 2026 01:29:02 +0800 [thread overview]
Message-ID: <20260505172903.33271-1-wens@kernel.org> (raw)
While the design of the NanoPi R4S is based on the common NanoPi 4
family, it is trimmed down a lot.
Disable all the peripherals on the SoC that are not used, and delete
all the external components that are not present.
Signed-off-by: Chen-Yu Tsai <wens@kernel.org>
---
.../boot/dts/rockchip/rk3399-nanopi-r4s.dtsi | 68 +++++++++++++++++++
1 file changed, 68 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi
index 3a9a10f531bd..4274d1b6e80a 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi
@@ -66,16 +66,41 @@ &emmc_phy {
status = "disabled";
};
+/* No USB type-C PD power manager */
+/delete-node/ &fusb0;
+
+&i2c1 {
+ status = "disabled";
+};
+
&i2c4 {
status = "disabled";
};
+&i2c7 {
+ status = "disabled";
+};
+
+&i2s2 {
+ status = "disabled";
+};
+
+&hdmi {
+ status = "disabled";
+};
+
+&hdmi_sound {
+ status = "disabled";
+};
+
&pcie0 {
num-lanes = <1>;
vpcie3v3-supply = <&vcc3v3_sys>;
};
&pinctrl {
+ /delete-node/ fusb30x;
+
gpio-leds {
/delete-node/ status-led-pin;
@@ -101,14 +126,21 @@ reset_button_pin: reset-button-pin {
};
};
+&pwm0 {
+ status = "disabled";
+};
+
&sdhci {
status = "disabled";
};
&sdio0 {
+ /delete-property/ mmc-pwrseq;
status = "disabled";
};
+/delete-node/ &sdio_pwrseq;
+
&u2phy0_host {
phy-supply = <&vdd_5v>;
};
@@ -119,12 +151,48 @@ &u2phy1_host {
&uart0 {
status = "disabled";
+
+ /delete-node/ bluetooth;
};
+&u2phy1_host {
+ status = "disabled";
+};
+
+&usb_host1_ehci {
+ status = "disabled";
+};
+
+&usb_host1_ohci {
+ status = "disabled";
+};
&usbdrd_dwc3_0 {
dr_mode = "host";
};
+/delete-node/ &vbus_typec;
+
&vcc3v3_sys {
vin-supply = <&vcc5v0_sys>;
};
+
+&vopb {
+ status = "disabled";
+};
+
+&vopb_mmu {
+ status = "disabled";
+};
+
+&vopl {
+ status = "disabled";
+};
+
+&vopl_mmu {
+ status = "disabled";
+};
+
+/delete-node/ &bt_host_wake_l;
+/delete-node/ &bt_reg_on_h;
+/delete-node/ &bt_wake_l;
+/delete-node/ &wifi_reg_on_h;
--
2.47.3
reply other threads:[~2026-05-05 17:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260505172903.33271-1-wens@kernel.org \
--to=wens@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-rockchip@lists.infradead.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