Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "John Madieu" <john.madieu.xa@bp.renesas.com>
Cc: conor+dt@kernel.org, wsa+renesas@sang-engineering.com,
	devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 1/8] dt-bindings: clock: renesas: Add audio clock inputs for RZ/V2H family
Date: Mon, 25 May 2026 11:19:19 +0000	[thread overview]
Message-ID: <20260525111920.15F771F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260525110603.4018170-2-john.madieu.xa@bp.renesas.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Strict array ordering prevents the independent use of newly added optional clocks.
--

commit 3723d06ba80fe72a3e7492af52e5e54aa0f36b03
Author: John Madieu <john.madieu.xa@bp.renesas.com>

dt-bindings: clock: renesas: Add audio clock inputs for RZ/V2H family

This commit updates the clock bindings for the RZ/V2H family SoCs to include
the optional external audio clock inputs AUDIO_CLKB and AUDIO_CLKC. The
AUDIO_CLKA input is fed internally and thus does not require a binding entry.

> diff --git a/Documentation/devicetree/bindings/clock/renesas,rzv2h-cpg.yaml b/Documentation/devicetree/bindings/clock/renesas,rzv2h-cpg.yaml
> --- a/Documentation/devicetree/bindings/clock/renesas,rzv2h-cpg.yaml
> +++ b/Documentation/devicetree/bindings/clock/renesas,rzv2h-cpg.yaml
> @@ -26,16 +26,22 @@ properties:
>      maxItems: 1
>  
>    clocks:
> +    minItems: 3
>      items:
>        - description: AUDIO_EXTAL clock input
>        - description: RTXIN clock input
>        - description: QEXTAL clock input
> +      - description: AUDIO_CLKB clock input
> +      - description: AUDIO_CLKC clock input
>  
>    clock-names:
> +    minItems: 3
>      items:
>        - const: audio_extal
>        - const: rtxin
>        - const: qextal
> +      - const: audio_clkb
> +      - const: audio_clkc

[Severity: Medium]
Will this strict array ordering prevent the independent use of the newly
added optional clocks?

Because JSON schema validates arrays strictly by position based on the items
list, if a hardware board connects AUDIO_CLKC but does not connect AUDIO_CLKB,
the device tree node would provide an array of 4 clocks where the 4th name
is audio_clkc.

When dt_binding_check evaluates this, won't it check the 4th element against
the schema's expectation of audio_clkb and fail, incorrectly rejecting a valid
hardware configuration?

Should this use an anyOf block enumerating the valid permutations of optional
clocks to avoid forcing users to write incorrect device trees to pass
validation?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260525110603.4018170-1-john.madieu.xa@bp.renesas.com?part=1

  reply	other threads:[~2026-05-25 11:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 11:05 [PATCH v4 0/8] arm64: dts: renesas: Add RZ/G3E audio enablement John Madieu
2026-05-25 11:05 ` [PATCH v4 1/8] dt-bindings: clock: renesas: Add audio clock inputs for RZ/V2H family John Madieu
2026-05-25 11:19   ` sashiko-bot [this message]
2026-05-25 16:56     ` Conor Dooley
2026-05-25 11:05 ` [PATCH v4 2/8] clk: renesas: r9a09g047: Add audio clock and reset support John Madieu
2026-05-25 11:05 ` [PATCH v4 3/8] arm64: dts: renesas: rzv2h: Add audio clock inputs John Madieu
2026-05-25 11:41   ` sashiko-bot
2026-05-25 11:05 ` [PATCH v4 4/8] arm64: dts: renesas: r9a09g047: Add RZ/G3E Sound support John Madieu
2026-05-25 11:06 ` [PATCH v4 5/8] arm64: dts: renesas: rzg3e-smarc-som: Add Versa3 clock generator John Madieu
2026-05-25 11:06 ` [PATCH v4 6/8] arm64: dts: renesas: rzg3e-smarc-som: Add I2C1 support John Madieu
2026-05-25 11:06 ` [PATCH v4 7/8] arm64: dts: renesas: rzg3e-smarc-som: add audio pinmux definitions John Madieu
2026-05-25 12:28   ` sashiko-bot
2026-05-25 11:06 ` [PATCH v4 8/8] arm64: dts: renesas: r9a09g047e57-smarc: add DA7212 audio codec support John Madieu
2026-05-25 12:49   ` sashiko-bot

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=20260525111920.15F771F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=john.madieu.xa@bp.renesas.com \
    --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