From: sashiko-bot@kernel.org
To: "Biju Das" <biju.das.jz@bp.renesas.com>
Cc: wsa+renesas@sang-engineering.com, linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 1/8] clk: renesas: r9a08g046: Add TSU,ADC1 clocks and reset
Date: Fri, 18 Sep 2026 15:23:47 +0000 [thread overview]
Message-ID: <20260918152347.D7F881F0089A@smtp.kernel.org> (raw)
In-Reply-To: <20260918150730.122056-2-biju.das.jz@bp.renesas.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] clk: renesas: incorrect MSTOP bus for ADC1 and TSU clocks
--
commit e17a7f8fc3947f6cab70a435b3bbdc24af6057ce
Author: Biju Das <biju.das.jz@bp.renesas.com>
clk: renesas: r9a08g046: Add TSU,ADC1 clocks and reset
This commit adds clock P20, module clocks for ADC1 and TSU, and the
corresponding resets for the RZ/G3S (R9A08G046) SoC.
> diff --git a/drivers/clk/renesas/r9a08g046-cpg.c b/drivers/clk/renesas/r9a08g046-cpg.c
> index 22821321a1d37..2c5ca5ab5f578 100644
> --- a/drivers/clk/renesas/r9a08g046-cpg.c
> +++ b/drivers/clk/renesas/r9a08g046-cpg.c
[ ... ]
> @@ -559,6 +560,12 @@ static const struct rzg2l_mod_clk r9a08g046_mod_clks[] = {
> MSTOP(BUS_MCPU2, BIT(0))),
> DEF_MOD("gpio_hclk", R9A08G046_GPIO_HCLK, R9A08G046_OSCCLK, 0x598, 0,
> MSTOP(BUS_PERI_CPU, BIT(6))),
> + DEF_MOD("adc1_adclk", R9A08G046_ADC1_ADCLK, R9A08G046_CLK_P20, 0x5a8, 2,
> + MSTOP(BUS_PERI_VIDEO, BIT(14))),
> + DEF_MOD("adc1_pclk", R9A08G046_ADC1_PCLK, R9A08G046_CLK_P20, 0x5a8, 3,
> + MSTOP(BUS_PERI_VIDEO, BIT(14))),
> + DEF_MOD("tsu_pclk", R9A08G046_TSU_PCLK, R9A08G046_CLK_P20, 0x5ac, 0,
> + MSTOP(BUS_PERI_VIDEO, BIT(15))),
[Severity: Medium]
Looking at r9a08g046_mod_clks in drivers/clk/renesas/r9a08g046-cpg.c, are
the MSTOP bus assignments for these ADC1 and TSU clocks correct?
Based on similar architecture mapping in RZ/G2L and RZ/G3S (which use
BUS_MCPU2 for these identical register offsets), it seems this code
might be assigning BUS_PERI_VIDEO when it should use BUS_MCPU2.
If these devices actually reside on BUS_MCPU2, could this regression
cause a write to the wrong MSTOP register during initialization or
runtime PM? This might cause the ADC1 and TSU clocks to fail to ungate
while concurrently corrupting bits 14 and 15 of the video module stop
register when the devices are probed.
> DEF_MOD("pci_aclk", R9A08G046_PCI_ACLK, R9A08G046_CLK_P1, 0x608, 0,
> MSTOP(BUS_PERI_COM, BIT(10))),
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918150730.122056-1-biju.das.jz@bp.renesas.com?part=1
next prev parent reply other threads:[~2026-09-18 15:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 15:07 [PATCH v2 0/8] Add Renesas RZ/G3L TSU support Biju Das
2026-09-18 15:07 ` [PATCH v2 1/8] clk: renesas: r9a08g046: Add TSU,ADC1 clocks and reset Biju Das
2026-09-18 15:23 ` sashiko-bot [this message]
2026-09-18 15:34 ` Biju Das
2026-09-18 15:07 ` [PATCH v2 2/8] dt-bindings: thermal: r9a08g045-tsu: Document RZ/G3L TSU Biju Das
2026-09-20 17:39 ` Jonathan Cameron
2026-09-18 15:07 ` [PATCH v2 3/8] thermal/drivers/renesas/rzg3s: Convert calibration defaults to per-SoC match data Biju Das
2026-09-20 17:39 ` Jonathan Cameron
2026-09-18 15:07 ` [PATCH v2 4/8] thermal/drivers/renesas/rzg3s: Add RZ/G3L TSU support Biju Das
2026-09-20 17:39 ` Jonathan Cameron
2026-09-21 1:44 ` Biju Das
2026-09-21 3:28 ` Jonathan Cameron
2026-09-21 4:38 ` Biju Das
2026-09-18 15:07 ` [PATCH v2 5/8] dt-bindings: iio: adc: renesas,rzg2l-adc: Make '#io-channel-cells' required for R9A08G045 Biju Das
2026-09-25 1:53 ` Rob Herring (Arm)
2026-09-18 15:07 ` [PATCH v2 6/8] dt-bindings: iio: adc: renesas,rzg2l-adc: Document RZ/G3L ADC for TSU Biju Das
2026-09-20 17:39 ` Jonathan Cameron
2026-09-21 2:03 ` Biju Das
2026-09-21 3:29 ` Jonathan Cameron
2026-09-21 4:50 ` Biju Das
2026-09-18 15:07 ` [PATCH v2 7/8] iio: adc: rzg2l_adc: Add RZ/G3L ADC support " Biju Das
2026-09-18 15:07 ` [PATCH v2 8/8] arm64: dts: renesas: r9a08g046: Enable TSU Biju Das
2026-09-18 15:22 ` sashiko-bot
2026-09-18 15:40 ` Biju Das
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=20260918152347.D7F881F0089A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=linux-clk@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.