Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: devicetree@vger.kernel.org, wsa+renesas@sang-engineering.com,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: renesas: r9a09g077: Add RTC node
Date: Mon, 24 Aug 2026 08:13:33 +0000	[thread overview]
Message-ID: <20260824081334.21DAE1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260824075936.2904336-2-prabhakar.mahadev-lad.rj@bp.renesas.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Build failure due to undefined macro `R9A09G077_PCLKRTC`.
--

--- Patch [1]: [PATCH 1/3] arm64: dts: renesas: r9a09g077: Add RTC node ---
commit 2ac601db99f828037f74c28a1b191a0855d1fe45
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>

arm64: dts: renesas: r9a09g077: Add RTC node

This patch adds the Real Time Clock (RTC) node to the Renesas R9A09G077 SoC
device tree include file.

> diff --git a/arch/arm64/boot/dts/renesas/r9a09g077.dtsi b/arch/arm64/boot/dts/renesas/r9a09g077.dtsi
> --- a/arch/arm64/boot/dts/renesas/r9a09g077.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r9a09g077.dtsi
[ ... ]
> @@ -1146,6 +1146,19 @@ pinctrl: pinctrl@802c0000 {
>  			power-domains = <&cpg>;
>  		};
>  
> +		rtc0: rtc@81009000 {
> +			compatible = "renesas,r9a09g077-rtc";
> +			reg = <0 0x81009000 0 0x1000>;
> +			interrupts = <GIC_SPI 495 IRQ_TYPE_EDGE_RISING>,
> +				     <GIC_SPI 497 IRQ_TYPE_EDGE_RISING>,
> +				     <GIC_SPI 496 IRQ_TYPE_EDGE_RISING>;
> +			interrupt-names = "alarm", "timer", "pps";
> +			clocks = <&cpg CPG_MOD 605>, <&cpg CPG_CORE R9A09G077_PCLKRTC>;

[Severity: Low]
Is there a missing prerequisite patch that defines R9A09G077_PCLKRTC?

Since R9A09G077_PCLKRTC is not defined in the tree, the C preprocessor leaves
it as a literal string. When dtc parses the file, it encounters the unquoted
string inside a cell array and throws a syntax error, causing a build failure
when compiling the device trees.

> +			clock-names = "hclk", "xtal";
> +			power-domains = <&cpg>;
> +			status = "disabled";
> +		};
> +
[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260824075936.2904336-1-prabhakar.mahadev-lad.rj@bp.renesas.com?part=1

  reply	other threads:[~2026-08-24  8:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24  7:59 [PATCH 0/3] Enable RTC support on RZ/T2H and RZ/N2H SoCs Prabhakar
2026-08-24  7:59 ` [PATCH 1/3] arm64: dts: renesas: r9a09g077: Add RTC node Prabhakar
2026-08-24  8:13   ` sashiko-bot [this message]
2026-08-25 12:22   ` Geert Uytterhoeven
2026-08-24  7:59 ` [PATCH 2/3] arm64: dts: renesas: r9a09g087: " Prabhakar
2026-08-24  8:11   ` sashiko-bot
2026-08-25 12:22   ` Geert Uytterhoeven
2026-08-24  7:59 ` [PATCH 3/3] arm64: dts: renesas: rzt2h-n2h-evk: Enable RTC support Prabhakar
2026-08-24  8:08   ` sashiko-bot
2026-08-24  9:25   ` Wolfram Sang
2026-08-24 12:32     ` Geert Uytterhoeven
2026-08-24  9:30   ` Wolfram Sang
2026-08-25 12:23   ` Geert Uytterhoeven

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=20260824081334.21DAE1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=prabhakar.csengg@gmail.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