From: Vladimir Zapolskiy <vz@mleia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: 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>,
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: Re: [PATCH 1/2] dt-bindings: serial: 8250: Explicitly make LPC32xx UARTs compatible with 16550A
Date: Mon, 12 Jan 2026 12:06:33 +0200 [thread overview]
Message-ID: <7dbce9cc-e043-43ae-8d3a-a20b8ad2a5fb@mleia.com> (raw)
In-Reply-To: <20260112-hopeful-spiffy-antelope-334765@quoll>
On 1/12/26 11:25, Krzysztof Kozlowski wrote:
> On Sat, Jan 10, 2026 at 04:46:46AM +0200, Vladimir Zapolskiy wrote:
>> NXP LPC32xx SoC has 4 16550A compatible UARTs with 64 byte TX and RX FIFO
>> sizes, and the platform UART hardware is well supported as a standard
>> 16550A UART.
>
> Driver uses dedicated driver/match data, so some context here about
> compatibility would be useful.
>
As the commit message says, 4 LPC32xx UARTs are NS16550A compatible, this
is the context of the change.
Any bootloader or operating system which does not locate "nxp,lpc3220-uart"
device driver shall use the general "ns16550" compatible device driver.
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2026-01-12 10:12 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 [this message]
2026-01-10 2:46 ` [PATCH 2/2] arm: dts: lpc32xx: Add ns16550a compatible value to UART device tree nodes Vladimir Zapolskiy
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=7dbce9cc-e043-43ae-8d3a-a20b8ad2a5fb@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=krzk@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