All of lore.kernel.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 0/4] Clear some dtbs_check warnings detected by snps-dw-apb-uart.yaml
Date: Wed, 19 May 2021 22:19:10 +0800	[thread overview]
Message-ID: <20210519141914.8044-1-thunder.leizhen@huawei.com> (raw)

The Synopsys DesignWare ABP UART is commonly used. Therefore, it is meaningful
to clear the warnings detected by snps-dw-apb-uart.yaml. I fixed everything I
could. The only problem left is that some serial port nodes do not have the
property 'interrupts'. I don't know their interrupt number, so there's no way
to fix it. By the way, is there a scenario where serial ports do not need to be
interrupted? If it exists, property 'interrupts' should not be defined as required.


Zhen Lei (4):
  arm64: dts: bitmain: normalize the node name of the UART devices
  arm64: dts: broadcom: normalize the node name of the UART devices
  arm64: dts: realtek: rtd16xx: normalize the node name of the UART
    devices
  arm64: dts: synaptics: normalize the node name of the UART devices

 arch/arm64/boot/dts/bitmain/bm1880.dtsi             | 6 +++---
 arch/arm64/boot/dts/broadcom/stingray/stingray.dtsi | 8 ++++----
 arch/arm64/boot/dts/realtek/rtd16xx.dtsi            | 6 +++---
 arch/arm64/boot/dts/synaptics/berlin4ct.dtsi        | 2 +-
 4 files changed, 11 insertions(+), 11 deletions(-)

-- 
2.21.1



WARNING: multiple messages have this Message-ID (diff)
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 0/4] Clear some dtbs_check warnings detected by snps-dw-apb-uart.yaml
Date: Wed, 19 May 2021 22:19:10 +0800	[thread overview]
Message-ID: <20210519141914.8044-1-thunder.leizhen@huawei.com> (raw)

The Synopsys DesignWare ABP UART is commonly used. Therefore, it is meaningful
to clear the warnings detected by snps-dw-apb-uart.yaml. I fixed everything I
could. The only problem left is that some serial port nodes do not have the
property 'interrupts'. I don't know their interrupt number, so there's no way
to fix it. By the way, is there a scenario where serial ports do not need to be
interrupted? If it exists, property 'interrupts' should not be defined as required.


Zhen Lei (4):
  arm64: dts: bitmain: normalize the node name of the UART devices
  arm64: dts: broadcom: normalize the node name of the UART devices
  arm64: dts: realtek: rtd16xx: normalize the node name of the UART
    devices
  arm64: dts: synaptics: normalize the node name of the UART devices

 arch/arm64/boot/dts/bitmain/bm1880.dtsi             | 6 +++---
 arch/arm64/boot/dts/broadcom/stingray/stingray.dtsi | 8 ++++----
 arch/arm64/boot/dts/realtek/rtd16xx.dtsi            | 6 +++---
 arch/arm64/boot/dts/synaptics/berlin4ct.dtsi        | 2 +-
 4 files changed, 11 insertions(+), 11 deletions(-)

-- 
2.21.1



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

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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 14:19 Zhen Lei [this message]
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   ` Zhen Lei
2021-05-19 14:19 ` [PATCH 2/4] arm64: dts: broadcom: " Zhen Lei
2021-05-19 14:19   ` Zhen Lei
2021-05-20 18:45   ` Florian Fainelli
2021-05-20 18:45     ` Florian Fainelli
2021-05-19 14:19 ` [PATCH 3/4] arm64: dts: realtek: rtd16xx: " Zhen Lei
2021-05-19 14:19   ` Zhen Lei
2021-05-19 14:31   ` Andreas Färber
2021-05-19 14:31     ` Andreas Färber
2021-05-19 14:46     ` Leizhen (ThunderTown)
2021-05-19 14:46       ` Leizhen (ThunderTown)
2021-05-19 14:19 ` [PATCH 4/4] arm64: dts: synaptics: " Zhen Lei
2021-05-19 14:19   ` 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-1-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.