From: sashiko-bot@kernel.org
To: "Jisheng Zhang" <jszhang@kernel.org>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: serial: snps-dw-apb-uart: Add Synaptics sl2610 uart
Date: Mon, 05 Oct 2026 15:49:09 +0000 [thread overview]
Message-ID: <20261005154909.BCAA21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261005151918.25259-1-jszhang@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: missing minItems: 2 constraint for syna,sl2610-uart resets
--
commit d2c2a625dcf17e541f9ec792d85888075ee11605
Author: Jisheng Zhang <jszhang@kernel.org>
dt-bindings: serial: snps-dw-apb-uart: Add Synaptics sl2610 uart
Add the compatible for the UARTs of the Synaptics SL2610, which are
compatible with the Synopsys DesignWare APB UART.
> diff --git a/Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml b/Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml
> index 664305de4986f..a40f2737e71b5 100644
> --- a/Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml
> +++ b/Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml
> @@ -34,7 +34,16 @@ allOf:
> properties:
> resets:
> minItems: 2
> - else:
> +
> + - if:
> + not:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - starfive,jh7110-uart
> + - syna,sl2610-uart
[Severity: Low]
Does this compatible string also need to be added to the if-then block
enforcing the minItems: 2 constraint?
This block explicitly exempts syna,sl2610-uart from the maxItems: 1
single-reset constraint, indicating it requires 2 resets. However, the
block immediately above this (which enforces minItems: 2 for
starfive,jh7110-uart) was not updated to include syna,sl2610-uart.
As a result, device trees for syna,sl2610-uart with only 1 reset will
silently pass schema validation.
> + then:
> properties:
> resets:
> maxItems: 1
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261005151918.25259-1-jszhang@kernel.org?part=1
next prev parent reply other threads:[~2026-10-05 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 15:19 [PATCH v2] dt-bindings: serial: snps-dw-apb-uart: Add Synaptics sl2610 uart Jisheng Zhang
2026-10-05 15:49 ` sashiko-bot [this message]
2026-10-07 13:04 ` Conor Dooley
2026-10-08 13:49 ` Jisheng Zhang
2026-10-09 15:44 ` Conor Dooley
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=20261005154909.BCAA21F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jszhang@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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