Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: devicetree@vger.kernel.org, linux-serial@vger.kernel.org,
	conor+dt@kernel.org, robh@kernel.org,
	wsa+renesas@sang-engineering.com
Subject: Re: [PATCH] dt-bindings: serial: renesas,scif: Increase number of DMA channels to 6
Date: Thu, 17 Sep 2026 14:14:43 +0000	[thread overview]
Message-ID: <20260917141443.B68B91F000FF@smtp.kernel.org> (raw)
In-Reply-To: <4d6e5ac045af387dde8ef3810ce08c7cb079fc29.1789653872.git.geert@linux-m68k.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: schema allows 6 DMAs for older SCIF hardware
--

commit ca96f7e40234020713acb3baf706d0b07d5dcc48
Author: Geert Uytterhoeven <geert@linux-m68k.org>

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

This commit updates the renesas,scif device tree binding to allow up to 6
DMA channels. This supports the R-Car X5H hardware where SCIF serial
interfaces are connected to three DMACs.

> 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 modifying the global properties.dmas limit relax the schema too much
for older hardware variants? By changing the top-level maxItems to 6, older
SCIF generations (like Gen1-Gen4) will now pass dt_binding_check even if a
device tree incorrectly specifies more than 4 DMA channels. Should this
expanded limit be constrained to the R-Car X5H compatible string using an
if-then conditional block instead?

>      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 changing the global properties.dma-names maxItems to 6
allow invalid configurations for older SoCs to pass validation? If previous
hardware only supports up to 4 DMA names, applying this limit globally
bypasses the stricter constraints of older generations.

>      items:
>        enum:
>          - tx

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/4d6e5ac045af387dde8ef3810ce08c7cb079fc29.1789653872.git.geert@linux-m68k.org?part=1

  reply	other threads:[~2026-09-17 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 14:06 [PATCH] dt-bindings: serial: renesas,scif: Increase number of DMA channels to 6 Geert Uytterhoeven
2026-09-17 14:14 ` sashiko-bot [this message]
2026-09-17 14:27   ` Geert Uytterhoeven
2026-09-17 16:27 ` Wolfram Sang

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=20260917141443.B68B91F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --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