Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Linus Walleij" <linusw@kernel.org>
Cc: robh@kernel.org, devicetree@vger.kernel.org,
	media-ci@linuxtv.org, wsa+renesas@sang-engineering.com,
	conor+dt@kernel.org
Subject: Re: [PATCH v2 3/4] arm64: dts: renesas: r9a09g057: Add IVC and ISP nodes
Date: Fri, 25 Sep 2026 13:08:00 +0000	[thread overview]
Message-ID: <20260925130800.C388F1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260925-mali-c55-renesas-dts-v2-3-69f728a474a2@kernel.org>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] arm64: dts: renesas: swapped vclk and hclk clock/reset mapping in mali-c55 ISP node
- [High] arm64: dts: renesas: missing power-domains property in mali-c55 ISP node
--

commit f1f95e2c7f1fc7d73c0351518cd19bf0ac773a31
Author: Daniel Scally <dan.scally@ideasonboard.com>

arm64: dts: renesas: r9a09g057: Add IVC and ISP nodes

Add the Input Video Control Block and Arm Mali-C55 ISP to the device
tree file for the RZ/V2H(P) SoC.

> diff --git a/arch/arm64/boot/dts/renesas/r9a09g057.dtsi b/arch/arm64/boot/dts/renesas/r9a09g057.dtsi
> index 639693d464a77..f04180c35866a 100644
> --- a/arch/arm64/boot/dts/renesas/r9a09g057.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r9a09g057.dtsi
[ ... ]
> +		isp: isp@16080000 {
> +			compatible = "arm,mali-c55";
> +			reg = <0 0x16080000 0 0x80000>;

[Severity: High]
Does this node need a power-domains property?

The isp node appears to omit power-domains = <&cpg>;. On Renesas SoCs, this
property attaches the device to the Clock Pulse Generator (CPG) generic power
domain, which is responsible for clearing the BUS_MSTOP bits during
pm_runtime_resume. 

Without it, pm_runtime_resume_and_get() in the driver might not trigger the
genpd domain hooks to clear MSTOP, which could cause register accesses to hang
the bus or leave the hardware inaccessible.

> +			clocks = <&cpg CPG_MOD 0xe2>, <&cpg CPG_MOD 0xe4>,
> +				 <&cpg CPG_MOD 0xe5>;
> +			clock-names = "vclk", "aclk", "hclk";

[Severity: High]
Are the vclk and hclk clock mappings swapped here?

The arm,mali-c55 driver expects vclk to be the video clock and hclk to be the
AHB register clock. Here, vclk is assigned to CPG_MOD 0xe2 (isp_0_reg_aclk)
and hclk is assigned to CPG_MOD 0xe5 (isp_0_isp_sclk). 

This appears to reverse their roles and could cause the driver to configure
the wrong clock frequencies.

> +			interrupts = <GIC_SPI 859 IRQ_TYPE_LEVEL_HIGH>,
> +				     <GIC_SPI 865 IRQ_TYPE_EDGE_RISING>,
> +				     <GIC_SPI 866 IRQ_TYPE_EDGE_RISING>;
> +			resets = <&cpg 0xd2>, <&cpg 0xd1>, <&cpg 0xd3>;
> +			reset-names = "vresetn", "aresetn", "hresetn";

[Severity: High]
Are the vresetn and hresetn reset mappings also swapped?

Similar to the clocks, this maps the register reset (0xd2 ISP_0_REG_ARESETN)
to vresetn and the ISP video reset (0xd3) to hresetn. This could lead to
reset domains being incorrectly managed, resulting in hardware initialization
failures.

> +			status = "disabled";
> +
> +			port {
> +				isp_in: endpoint {
> +					remote-endpoint = <&ivc_out>;
> +				};
> +			};
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260925-mali-c55-renesas-dts-v2-0-69f728a474a2@kernel.org?part=3

  reply	other threads:[~2026-09-25 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 12:56 [PATCH v2 0/4] arm64: dts: renesas: Enable ISP and IVC on RZ/V2H EVK Linus Walleij
2026-09-25 12:56 ` [PATCH v2 1/4] dt-bindings: media: renesas,r9a09g057-ivc: Describe additional interrupts Linus Walleij
2026-09-25 16:44   ` Conor Dooley
2026-09-25 12:56 ` [PATCH v2 2/4] dt-bindings: media: arm,mali-c55: Describe DMA line-tick interrupts Linus Walleij
2026-09-25 12:56 ` [PATCH v2 3/4] arm64: dts: renesas: r9a09g057: Add IVC and ISP nodes Linus Walleij
2026-09-25 13:08   ` sashiko-bot [this message]
2026-09-25 12:56 ` [PATCH v2 4/4] arm64: dts: renesas: r9a09g057h44-rzv2h-evk: Add ISP and IVC nodes Linus Walleij
2026-09-25 13:06   ` Linus Walleij

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=20260925130800.C388F1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linusw@kernel.org \
    --cc=media-ci@linuxtv.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