From: Nishanth Menon <nm@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Jan Kiszka <jan.kiszka@siemens.com>, Andrew Davis <afd@ti.com>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH V2 4/4] arm64: dts: ti: k3-am65-iot2050-common: Rename rtc8564 nodename
Date: Tue, 6 Jun 2023 11:06:43 -0500 [thread overview]
Message-ID: <20230606160643.3618390-5-nm@ti.com> (raw)
In-Reply-To: <20230606160643.3618390-1-nm@ti.com>
Just use "rtc" as the nodename to better match with the bindings.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
No change since V1
V1: https://lore.kernel.org/r/20230424144949.244135-8-nm@ti.com
arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
index 96ac2b476b11..679857ca95ea 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
@@ -483,7 +483,7 @@ &main_i2c0 {
pinctrl-0 = <&main_i2c0_pins_default>;
clock-frequency = <400000>;
- rtc: rtc8564@51 {
+ rtc: rtc@51 {
compatible = "nxp,pcf8563";
reg = <0x51>;
};
--
2.40.0
prev parent reply other threads:[~2023-06-06 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 16:06 [PATCH V2 0/4] arm64: dts: ti: k3-am65: dtbs_check warnings fixups Nishanth Menon
2023-06-06 16:06 ` [PATCH V2 1/4] arm64: dts: ti: k3-am65-main: Fix mux controller node name Nishanth Menon
2023-06-06 16:29 ` Andrew Davis
2023-06-06 17:07 ` Nishanth Menon
2023-06-06 16:06 ` [PATCH V2 2/4] arm64: dts: ti: k3-am65-main: Fix mcan " Nishanth Menon
2023-06-06 16:06 ` [PATCH V2 3/4] arm64: dts: ti: k3-am65-main: Drop deprecated ti,otap-del-sel property Nishanth Menon
2023-06-06 16:06 ` Nishanth Menon [this message]
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=20230606160643.3618390-5-nm@ti.com \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®