public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Zhen Lei <thunder.leizhen@huawei.com>
To: "Manivannan Sadhasivam" <mani@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>, "Ray Jui" <rjui@broadcom.com>,
	"Scott Branden" <sbranden@broadcom.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Jisheng Zhang" <Jisheng.Zhang@synaptics.com>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	linux-realtek-soc <linux-realtek-soc@lists.infradead.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	devicetree <devicetree@vger.kernel.org>
Cc: Zhen Lei <thunder.leizhen@huawei.com>
Subject: [PATCH 3/4] arm64: dts: realtek: rtd16xx: normalize the node name of the UART devices
Date: Wed, 19 May 2021 22:19:13 +0800	[thread overview]
Message-ID: <20210519141914.8044-4-thunder.leizhen@huawei.com> (raw)
In-Reply-To: <20210519141914.8044-1-thunder.leizhen@huawei.com>

Change the node name of the UART devices to match
"^serial(@[0-9a-f,]+)*$".

Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
---
 arch/arm64/boot/dts/realtek/rtd16xx.dtsi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/arm64/boot/dts/realtek/rtd16xx.dtsi b/arch/arm64/boot/dts/realtek/rtd16xx.dtsi
index afba5f04c8ec..bf4d9e917925 100644
--- a/arch/arm64/boot/dts/realtek/rtd16xx.dtsi
+++ b/arch/arm64/boot/dts/realtek/rtd16xx.dtsi
@@ -195,7 +195,7 @@
 };
 
 &iso {
-	uart0: serial0@800 {
+	uart0: serial@800 {
 		compatible = "snps,dw-apb-uart";
 		reg = <0x800 0x400>;
 		reg-shift = <2>;
@@ -207,7 +207,7 @@
 };
 
 &misc {
-	uart1: serial1@200 {
+	uart1: serial@200 {
 		compatible = "snps,dw-apb-uart";
 		reg = <0x200 0x400>;
 		reg-shift = <2>;
@@ -217,7 +217,7 @@
 		status = "disabled";
 	};
 
-	uart2: serial2@400 {
+	uart2: serial@400 {
 		compatible = "snps,dw-apb-uart";
 		reg = <0x400 0x400>;
 		reg-shift = <2>;
-- 
2.21.1



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-05-19 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 14:19 [PATCH 0/4] Clear some dtbs_check warnings detected by snps-dw-apb-uart.yaml Zhen Lei
2021-05-19 14:19 ` [PATCH 1/4] arm64: dts: bitmain: normalize the node name of the UART devices Zhen Lei
2021-05-19 14:19 ` [PATCH 2/4] arm64: dts: broadcom: " Zhen Lei
2021-05-20 18:45   ` Florian Fainelli
2021-05-19 14:19 ` Zhen Lei [this message]
2021-05-19 14:31   ` [PATCH 3/4] arm64: dts: realtek: rtd16xx: " Andreas Färber
2021-05-19 14:46     ` Leizhen (ThunderTown)
2021-05-19 14:19 ` [PATCH 4/4] arm64: dts: synaptics: " Zhen Lei

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=20210519141914.8044-4-thunder.leizhen@huawei.com \
    --to=thunder.leizhen@huawei.com \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=afaerber@suse.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-realtek-soc@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=sebastian.hesselbarth@gmail.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