From: Shawn Lin <shawn.lin@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Shawn Lin <shawn.lin@rock-chips.com>
Subject: [PATCH 1/4] arm64: dts: rockchip: Remove broken-cd on Rock 5 ITX SDIO
Date: Wed, 23 Sep 2026 15:11:35 +0800 [thread overview]
Message-ID: <1790147498-47766-2-git-send-email-shawn.lin@rock-chips.com> (raw)
In-Reply-To: <1790147498-47766-1-git-send-email-shawn.lin@rock-chips.com>
The M.2 E-KEY SDIO slot is non-removable, so broken-cd is meaningless
and contradicts non-removable. Drop it.
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
---
arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts b/arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts
index 6f25e08..241df3f 100644
--- a/arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts
@@ -895,7 +895,6 @@
/* M.2 E-KEY */
&sdio {
- broken-cd;
bus-width = <4>;
cap-sdio-irq;
keep-power-in-suspend;
--
2.7.4
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-09-23 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 7:11 [PATCH 0/4] Clean up invalid MMC properties in Rockchip board DTs Shawn Lin
2026-09-23 7:11 ` Shawn Lin [this message]
2026-09-23 7:11 ` [PATCH 2/4] arm64: dts: rockchip: Remove cap-sd-highspeed on Rock Pi S eMMC Shawn Lin
2026-09-24 16:02 ` Jonas Karlman
2026-09-26 8:38 ` Shawn Lin
2026-09-23 7:11 ` [PATCH 3/4] arm64: dts: rockchip: Remove cap-mmc-highspeed from SD-only slots Shawn Lin
2026-09-23 7:11 ` [PATCH 4/4] ARM: dts: rockchip: Remove cap-mmc-highspeed from Omega4 sdmmc0 Shawn Lin
2026-09-30 18:49 ` (subset) [PATCH 0/4] Clean up invalid MMC properties in Rockchip board DTs 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=1790147498-47766-2-git-send-email-shawn.lin@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--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