From: FUKAUMI Naoki <naoki@radxa.com>
To: heiko@sntech.de
Cc: robh@kernel.org, conor+dt@kernel.org, inindev@gmail.com,
devicetree@vger.kernel.org, sebastian.reichel@collabora.com,
linux-rockchip@lists.infradead.org, alchark@gmail.com,
FUKAUMI Naoki <naoki@radxa.com>,
krzk+dt@kernel.org, dsimic@manjaro.org
Subject: [PATCH v2 4/4] arm64: dts: rockchip: cosmetic changes for Radxa ROCK 5B
Date: Mon, 2 Dec 2024 02:32:27 +0000 [thread overview]
Message-ID: <20241202023227.2671-5-naoki@radxa.com> (raw)
In-Reply-To: <20241202023227.2671-1-naoki@radxa.com>
no functional change is intended.
Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>
---
Changes in v2:
- none
---
arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts | 13 ++++---------
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts b/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts
index c29c61b4ffa7..3662549714e6 100644
--- a/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts
@@ -138,7 +138,7 @@ vcc5v0_sys: regulator-vcc5v0-sys {
vcc5v_usb: regulator-vcc5v-usb {
compatible = "regulator-fixed";
enable-active-high;
- gpio = <&gpio4 RK_PB0 GPIO_ACTIVE_HIGH>;
+ gpios = <&gpio4 RK_PB0 GPIO_ACTIVE_HIGH>;
pinctrl-names = "default";
pinctrl-0 = <&usb_host_pwren_h>;
regulator-name = "vcc5v_usb";
@@ -293,7 +293,7 @@ regulator-state-mem {
&i2c6 {
status = "okay";
- hym8563: rtc@51 {
+ rtc@51 {
compatible = "haoyu,hym8563";
reg = <0x51>;
#clock-cells = <0>;
@@ -309,7 +309,7 @@ hym8563: rtc@51 {
&i2c7 {
status = "okay";
- es8316: audio-codec@11 {
+ audio-codec@11 {
compatible = "everest,es8316";
reg = <0x11>;
assigned-clocks = <&cru I2S0_8CH_MCLKOUT>;
@@ -471,7 +471,6 @@ &sdhci {
};
&sdio {
- max-frequency = <200000000>;
bus-width = <4>;
cap-sdio-irq;
disable-wp;
@@ -481,9 +480,6 @@ &sdio {
non-removable;
pinctrl-names = "default";
pinctrl-0 = <&sdiom0_pins>;
- sd-uhs-sdr12;
- sd-uhs-sdr25;
- sd-uhs-sdr50;
sd-uhs-sdr104;
vmmc-supply = <&vcc3v3_wf>;
vqmmc-supply = <&vcc_1v8_s3>;
@@ -492,7 +488,6 @@ &sdio {
};
&sdmmc {
- max-frequency = <200000000>;
bus-width = <4>;
cap-mmc-highspeed;
cap-sd-highspeed;
@@ -530,7 +525,7 @@ &spi2 {
pmic@0 {
compatible = "rockchip,rk806";
- reg = <0x0>;
+ reg = <0>;
gpio-controller;
#gpio-cells = <2>;
interrupt-parent = <&gpio0>;
--
2.43.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-12-02 2:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 2:32 [PATCH v2 0/4] arm64: dts: rockchip: cosmetic changes for Radxa ROCK 5B FUKAUMI Naoki
2024-12-02 2:32 ` [PATCH v2 1/4] arm64: dts: rockchip: sort nodes in .dts " FUKAUMI Naoki
2024-12-02 2:32 ` [PATCH v2 2/4] arm64: dts: rockchip: sort nodes in root node " FUKAUMI Naoki
2024-12-02 2:32 ` [PATCH v2 3/4] arm64: dts: rockchip: sort properties in .dts " FUKAUMI Naoki
2024-12-02 2:32 ` FUKAUMI Naoki [this message]
2024-12-02 3:06 ` [PATCH v2 0/4] arm64: dts: rockchip: cosmetic changes " Dragan Simic
2024-12-02 3:58 ` FUKAUMI Naoki
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=20241202023227.2671-5-naoki@radxa.com \
--to=naoki@radxa.com \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=inindev@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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