public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vz@mleia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: Lubomir Rintel <lkundrak@v3.sk>,
	Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>,
	devicetree@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm: dts: lpc32xx: Add ns16550a compatible value to UART device tree nodes
Date: Sat, 10 Jan 2026 04:46:47 +0200	[thread overview]
Message-ID: <20260110024647.3389345-3-vz@mleia.com> (raw)
In-Reply-To: <20260110024647.3389345-1-vz@mleia.com>

NXP LPC32xx SoC has 4 16550A compatible UARTs with a difference of minor
significance, which is expectedly handled in the 8250 serial driver.

Reflect this fact in the platform device tree file by adding the expected
compatible value.

Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
---
 arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi b/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi
index e94df78def18..8fa1848943f8 100644
--- a/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi
+++ b/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi
@@ -263,8 +263,7 @@ i2s1: i2s@2009c000 {
 
 			/* UART5 first since it is the default console, ttyS0 */
 			uart5: serial@40090000 {
-				/* actually, ns16550a w/ 64 byte fifos! */
-				compatible = "nxp,lpc3220-uart";
+				compatible = "nxp,lpc3220-uart", "ns16550a";
 				reg = <0x40090000 0x1000>;
 				interrupts = <9 IRQ_TYPE_LEVEL_HIGH>;
 				reg-shift = <2>;
@@ -273,7 +272,7 @@ uart5: serial@40090000 {
 			};
 
 			uart3: serial@40080000 {
-				compatible = "nxp,lpc3220-uart";
+				compatible = "nxp,lpc3220-uart", "ns16550a";
 				reg = <0x40080000 0x1000>;
 				interrupts = <7 IRQ_TYPE_LEVEL_HIGH>;
 				reg-shift = <2>;
@@ -282,7 +281,7 @@ uart3: serial@40080000 {
 			};
 
 			uart4: serial@40088000 {
-				compatible = "nxp,lpc3220-uart";
+				compatible = "nxp,lpc3220-uart", "ns16550a";
 				reg = <0x40088000 0x1000>;
 				interrupts = <8 IRQ_TYPE_LEVEL_HIGH>;
 				reg-shift = <2>;
@@ -291,7 +290,7 @@ uart4: serial@40088000 {
 			};
 
 			uart6: serial@40098000 {
-				compatible = "nxp,lpc3220-uart";
+				compatible = "nxp,lpc3220-uart", "ns16550a";
 				reg = <0x40098000 0x1000>;
 				interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
 				reg-shift = <2>;
-- 
2.43.0


      parent reply	other threads:[~2026-01-10  2:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-10  2:46 [PATCH 0/2] arm: dts: lpc32xx: Specify compatibility of platform UARTs with 16550A Vladimir Zapolskiy
2026-01-10  2:46 ` [PATCH 1/2] dt-bindings: serial: 8250: Explicitly make LPC32xx UARTs compatible " Vladimir Zapolskiy
2026-01-12  9:25   ` Krzysztof Kozlowski
2026-01-12 10:06     ` Vladimir Zapolskiy
2026-01-10  2:46 ` Vladimir Zapolskiy [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=20260110024647.3389345-3-vz@mleia.com \
    --to=vz@mleia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --cc=piotr.wojtaszczyk@timesys.com \
    --cc=robh@kernel.org \
    /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