From: Daniel Palmer <daniel@0x0f.com>
To: devicetree@vger.kernel.org, linux-serial@vger.kernel.org,
robh+dt@kernel.org, andriy.shevchenko@linux.intel.com,
jirislaby@kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, romain.perier@gmail.com,
Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH 3/4] ARM: dts: mstar: Switch pm_uart to mstar,msc313-uart
Date: Thu, 24 Mar 2022 21:44:01 +0900 [thread overview]
Message-ID: <20220324124402.3631379-4-daniel@0x0f.com> (raw)
In-Reply-To: <20220324124402.3631379-1-daniel@0x0f.com>
The UART used in these SoCs is actually a variant of the dw apb uart.
Now there is a compatible string in that driver to handle the quirks
switch the compatible for pm_uart over to mstar,msc313-uart.
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
arch/arm/boot/dts/mstar-v7.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/mstar-v7.dtsi b/arch/arm/boot/dts/mstar-v7.dtsi
index c26ba9b7b6dd..8464a8f1b136 100644
--- a/arch/arm/boot/dts/mstar-v7.dtsi
+++ b/arch/arm/boot/dts/mstar-v7.dtsi
@@ -175,7 +175,7 @@ gpio: gpio@207800 {
};
pm_uart: uart@221000 {
- compatible = "ns16550a";
+ compatible = "mstar,msc313-uart", "snps,dw-apb-uart";
reg = <0x221000 0x100>;
reg-shift = <3>;
interrupts-extended = <&intc_irq GIC_SPI 34 IRQ_TYPE_LEVEL_HIGH>;
--
2.35.1
next prev parent reply other threads:[~2022-03-24 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 12:43 [PATCH 0/4] Add support for MStar MSC313 uarts Daniel Palmer
2022-03-24 12:43 ` [PATCH 1/4] dt-bindings: serial: snps-dw-apb-uart: Add " Daniel Palmer
2022-04-01 0:20 ` Rob Herring
2022-03-24 12:44 ` [PATCH 2/4] serial: 8250_dw: Add MStar MSC313 quirk Daniel Palmer
2022-03-24 13:58 ` Andy Shevchenko
2022-03-24 12:44 ` Daniel Palmer [this message]
2022-03-25 12:23 ` [PATCH 3/4] ARM: dts: mstar: Switch pm_uart to mstar,msc313-uart Romain Perier
2022-03-24 12:44 ` [PATCH 4/4] ARM: dts: mstar: Add second UART to base dtsi Daniel Palmer
2022-03-25 12:25 ` Romain Perier
2022-03-28 13:28 ` Rob Herring
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=20220324124402.3631379-4-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=romain.perier@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;
as well as URLs for NNTP newsgroup(s).