From: Conor Dooley <conor@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-serial@vger.kernel.org,
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>,
in file <devicetree@vger.kernel.org>,
"open list:TTY LAYER AND SERIAL DRIVERS"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: serial: 8250: add marvell,armada-38x-uart compatible
Date: Tue, 1 Sep 2026 18:51:41 +0100 [thread overview]
Message-ID: <20260901-corrode-unvented-4cf271941722@spud> (raw)
In-Reply-To: <20260901004203.49686-1-rosenp@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
On Mon, Aug 31, 2026 at 05:42:03PM -0700, Rosen Penev wrote:
> The Armada 38x and 98DX3236 SoCs use this compatible, either paired
> with "ns16550a" (armada-38x.dtsi) or on its own
> (armada-xp-98dx3236.dtsi). Neither form is covered by the 8250
> binding, so dtbs_check reports:
>
> serial@12000: failed to match any schema with compatible:
> ['marvell,armada-38x-uart', 'ns16550a']
>
> Add a standalone const entry and a two-string variant paired with
> "ns16550a".
Only one of these is correct, add one and fix the users.
Given there's match data, it's probably the standalone one.
pw-bot: changes-requested
Thanks,
Conor.
>
> Validated with make dt_binding_check (8250.yaml) and dt-validate on
> armada-38x and armada-xp 98DX3236 boards: the UART schema errors are
> gone.
>
> Assisted-by: opencode:big-pickle
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> Documentation/devicetree/bindings/serial/8250.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/serial/8250.yaml b/Documentation/devicetree/bindings/serial/8250.yaml
> index 8c2c177faf89..f71c6afe02f2 100644
> --- a/Documentation/devicetree/bindings/serial/8250.yaml
> +++ b/Documentation/devicetree/bindings/serial/8250.yaml
> @@ -109,6 +109,7 @@ properties:
> - const: aspeed,ast2500-vuart
> - const: intel,xscale-uart
> - const: mrvl,pxa-uart
> + - const: marvell,armada-38x-uart
> - const: nuvoton,wpcm450-uart
> - const: nuvoton,npcm750-uart
> - const: nvidia,tegra20-uart
> @@ -119,6 +120,9 @@ properties:
> - exar,xr16l2551
> - exar,xr16l2550
> - const: ns8250
> + - items:
> + - const: marvell,armada-38x-uart
> + - const: ns16550a
> - items:
> - enum:
> - altr,16550-FIFO32
> --
> 2.55.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-01 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 0:42 [PATCH] dt-bindings: serial: 8250: add marvell,armada-38x-uart compatible Rosen Penev
2026-09-01 0:49 ` sashiko-bot
2026-09-01 10:16 ` Krzysztof Kozlowski
2026-09-01 17:51 ` Conor Dooley [this message]
2026-09-02 21:34 ` Rosen Penev
2026-09-03 15:42 ` Conor Dooley
2026-09-03 18:58 ` Rosen Penev
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=20260901-corrode-unvented-4cf271941722@spud \
--to=conor@kernel.org \
--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-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=robh@kernel.org \
--cc=rosenp@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