Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: robh@kernel.org, devicetree@vger.kernel.org,
	linux-serial@vger.kernel.org, conor+dt@kernel.org,
	wsa+renesas@sang-engineering.com
Subject: Re: [PATCH v2] dt-bindings: serial: renesas,scif: Increase number of DMA channels to 6
Date: Tue, 22 Sep 2026 10:07:06 +0000	[thread overview]
Message-ID: <20260922100706.D32E41F000FF@smtp.kernel.org> (raw)
In-Reply-To: <4dc02f4ff8a63c2bd41b15359828ce9befd2da2f.1790071199.git.geert+renesas@glider.be>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: serial: missing conditional maxItems restriction for dmas
--

commit 24eddc5a7c6d95e9e9c7337b59a2dae1a4924772
Author: Geert Uytterhoeven <geert+renesas@glider.be>

dt-bindings: serial: renesas,scif: Increase number of DMA channels to 6

On R-Car X5H, SCIF serial interfaces are wired to three DMACs, hence
referring to up to six DMA channels.

> diff --git a/Documentation/devicetree/bindings/serial/renesas,scif.yaml b/Documentation/devicetree/bindings/serial/renesas,scif.yaml
> index 82f54446835e6..b465c93c8357f 100644
> --- a/Documentation/devicetree/bindings/serial/renesas,scif.yaml
> +++ b/Documentation/devicetree/bindings/serial/renesas,scif.yaml
> @@ -145,14 +145,14 @@ properties:
>  
>    dmas:
>      minItems: 2
> -    maxItems: 4
> +    maxItems: 6

[Severity: Low]
Does this global relaxation of maxItems in properties.dmas cause incomplete
validation for older hardware?

By increasing the top-level maxItems limit to 6 globally without a conditional
restriction, device trees for older generations of SoCs (Gen1 through Gen4)
that incorrectly specify 5 or 6 DMA channels will now silently pass schema
validation. Previously they would be caught as errors.

This triggers when a developer defines an invalid device tree node for an older
SoC with more than 4 DMA channels and runs make dt_binding_check.

>      description:
>        Must contain a list of pairs of references to DMA specifiers, one for
>        transmission, and one for reception.
>  
>    dma-names:
>      minItems: 2
> -    maxItems: 4
> +    maxItems: 6

[Severity: Low]
Similarly, does increasing the top-level maxItems limit in properties.dma-names
globally allow invalid device trees for older SoCs to bypass validation?

Without an if-then conditional block restricting older hardware, specifying 5
or 6 DMA channel names will silently pass schema checks for SoC generations
that only support up to 4.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/4dc02f4ff8a63c2bd41b15359828ce9befd2da2f.1790071199.git.geert+renesas@glider.be?part=1

  reply	other threads:[~2026-09-22 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 10:00 [PATCH v2] dt-bindings: serial: renesas,scif: Increase number of DMA channels to 6 Geert Uytterhoeven
2026-09-22 10:07 ` sashiko-bot [this message]
2026-09-28  6:29 ` Krzysztof Kozlowski

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=20260922100706.D32E41F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-serial@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wsa+renesas@sang-engineering.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