Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "John Madieu" <john.madieu.xa@bp.renesas.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
	wsa+renesas@sang-engineering.com
Subject: Re: [PATCH v5 2/4] arm64: dts: renesas: rzg3e-smarc-som: Add Versa3 clock generator
Date: Wed, 10 Jun 2026 07:51:52 +0000	[thread overview]
Message-ID: <20260610075152.D0F851F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260610074702.1743334-3-john.madieu.xa@bp.renesas.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The device tree configuration contradicts the commit message regarding Versa3 output 5.
--

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

arm64: dts: renesas: rzg3e-smarc-som: Add Versa3 clock generator

This patch adds the Renesas 5P35023 (Versa3) programmable clock generator
on the I2C2 bus for the RZ/G3E SMARC EVK. It configures outputs 0 through 4
to provide the necessary reference, audio, and Ethernet clocks.

> diff --git a/arch/arm64/boot/dts/renesas/rzg3e-smarc-som.dtsi b/arch/arm64/boot/dts/renesas/rzg3e-smarc-som.dtsi
> index d978619155d24..89428c804efb4 100644
> --- a/arch/arm64/boot/dts/renesas/rzg3e-smarc-som.dtsi
> +++ b/arch/arm64/boot/dts/renesas/rzg3e-smarc-som.dtsi

[ ... ]

> @@ -130,6 +136,20 @@ raa215300: pmic@12 {
>  
>  		interrupts-extended = <&pinctrl RZG3E_GPIO(S, 1) IRQ_TYPE_EDGE_FALLING>;
>  	};
> +
> +	versa3: clock-generator@68 {
> +		compatible = "renesas,5p35023";
> +		reg = <0x68>;
> +		#clock-cells = <1>;
> +		clocks = <&x2>;
> +
> +		assigned-clocks = <&versa3 0>, <&versa3 1>,
> +				  <&versa3 2>, <&versa3 3>,
> +				  <&versa3 4>, <&versa3 5>;
> +		assigned-clock-rates = <24000000>, <12288000>,
> +				       <11289600>, <12288000>,
> +				       <25000000>, <25000000>;

[Severity: Medium]
The commit message states "Output 5 (DIFF2) is left out, as it is not
connected on this board."  Is the inclusion of <&versa3 5> in the
assigned-clocks property intentional?

The arrays configure output 5 to 25MHz, which contradicts the commit
message and might unnecessarily enable an unconnected clock output.

> +	};
>  };
>  
>  &i3c {

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

  reply	other threads:[~2026-06-10  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  7:46 [PATCH v5 0/4] [PATCH v5 0/4] arm64: dts: renesas: Add RZ/G3E audio enablement John Madieu
2026-06-10  7:46 ` [PATCH v5 1/4] arm64: dts: renesas: r9a09g047: Add RZ/G3E Sound support John Madieu
2026-06-10  7:47 ` [PATCH v5 2/4] arm64: dts: renesas: rzg3e-smarc-som: Add Versa3 clock generator John Madieu
2026-06-10  7:51   ` sashiko-bot [this message]
2026-06-10  8:13   ` Biju Das
2026-06-10  7:47 ` [PATCH v5 3/4] arm64: dts: renesas: rzg3e-smarc-som: add audio pinmux definitions John Madieu
2026-06-10  7:47 ` [PATCH v5 4/4] arm64: dts: renesas: r9a09g047e57-smarc: add DA7212 audio codec support John Madieu
2026-06-10  8:01   ` 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=20260610075152.D0F851F00893@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