From: sashiko-bot@kernel.org
To: "Paul Elder" <paul.elder+renesas@ideasonboard.com>
Cc: linux-clk@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
media-ci@linuxtv.org, wsa+renesas@sang-engineering.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH 01/10] dt-bindings: clock: renesas,r8a78000-cpg: Add CPG_SGD4_VIO_DP_{TX,OTHER}
Date: Thu, 17 Sep 2026 12:09:38 +0000 [thread overview]
Message-ID: <20260917120938.751AA1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917-epaul-v7-3-rc1-x5h-vsp-fcp-v1-1-4c72d4e086dd@ideasonboard.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] abi: preliminary dt-bindings cause future ABI instability
--
commit db1a73966fe6909e57fbbac33c8b7f551e07a1fb
Author: Paul Elder <paul.elder+renesas@ideasonboard.com>
dt-bindings: clock: renesas,r8a78000-cpg: Add CPG_SGD4_VIO_DP_{TX,OTHER}
This commit adds preliminary clock definitions for CPG_SGD4_VIO_DP_TX and
CPG_SGD4_VIO_DP_OTHER to the r8a78000-cpg device tree bindings for testing
purposes.
> diff --git a/include/dt-bindings/clock/renesas,r8a78000-cpg.h b/include/dt-bindings/clock/renesas,r8a78000-cpg.h
> index 5851a29847f96..8c1a01e28ddbb 100644
> --- a/include/dt-bindings/clock/renesas,r8a78000-cpg.h
> +++ b/include/dt-bindings/clock/renesas,r8a78000-cpg.h
> @@ -12,5 +12,7 @@
> #define R8A78000_CPG_SGASYNCD16_PERW_BUS 2
> #define R8A78000_CPG_S0D4_PERE_MAIN 3 // FIXME Preliminary
> #define R8A78000_CPG_MSOCK_PERW_BUS 4 // FIXME Preliminary
> +#define R8A78000_CPG_SGD4_VIO_DP_TX 5 // FIXME Preliminary
> +#define R8A78000_CPG_SGD4_VIO_DP_OTHER 6 // FIXME Preliminary
[Severity: Medium]
Does introducing these explicitly preliminary clock indices into the device
tree bindings header create a risk for future ABI breakage?
Device tree bindings typically define a stable ABI between the hardware
description and the operating system kernel. If R8A78000_CPG_SGD4_VIO_DP_TX
or R8A78000_CPG_SGD4_VIO_DP_OTHER are changed, reordered, or removed when
the hardware documentation is finalized, it could break backward
compatibility with device trees created using these preliminary bindings.
Since follow-up patches in this series use these preliminary IDs, is there a
plan to stabilize these definitions before merging to avoid long-term
maintenance hazards?
>
> #endif /* __DT_BINDINGS_CLOCK_RENESAS_R8A78000_CPG_H__ */
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917-epaul-v7-3-rc1-x5h-vsp-fcp-v1-0-4c72d4e086dd@ideasonboard.com?part=1
next prev parent reply other threads:[~2026-09-17 12:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 12:04 [PATCH 00/10] media: rcar-fcp, vsp1: Enable on R-Car X5H Paul Elder
2026-09-17 12:04 ` [PATCH 01/10] dt-bindings: clock: renesas,r8a78000-cpg: Add CPG_SGD4_VIO_DP_{TX,OTHER} Paul Elder
2026-09-17 12:09 ` sashiko-bot [this message]
2026-09-18 1:03 ` Laurent Pinchart
2026-09-18 11:38 ` Krzysztof Kozlowski
2026-09-17 12:04 ` [PATCH 02/10] clk: renesas: r8a78000: Add clock for FCPV and VSP for SCP FW SDKv4.36 Paul Elder
2026-09-17 12:20 ` sashiko-bot
2026-09-18 1:11 ` Laurent Pinchart
2026-09-18 7:35 ` Geert Uytterhoeven
2026-09-17 12:04 ` [PATCH 03/10] pmdomain: renesas: r8a78000: Add maps for VIO " Paul Elder
2026-09-18 1:15 ` Laurent Pinchart
2026-09-17 12:04 ` [PATCH 04/10] arm64: renesas: r8a78000: Add FCPV[BI] nodes Paul Elder
2026-09-18 1:18 ` Laurent Pinchart
2026-09-17 12:04 ` [PATCH 05/10] arm64: renesas: r8a78000: Add VSP[BI] nodes Paul Elder
2026-09-18 1:21 ` Laurent Pinchart
2026-09-17 12:04 ` [PATCH 06/10] media: rcar-fcp: Check device revision at probe time Paul Elder
2026-09-17 12:12 ` sashiko-bot
2026-09-18 1:23 ` Laurent Pinchart
2026-09-17 12:04 ` [PATCH 07/10] media: rcar-fcp: Handle resets Paul Elder
2026-09-17 12:13 ` sashiko-bot
2026-09-18 1:28 ` Laurent Pinchart
2026-09-18 11:03 ` Biju Das
2026-09-18 11:11 ` Laurent Pinchart
2026-09-18 11:47 ` Biju Das
2026-09-17 12:04 ` [PATCH 08/10] media: vsp1: Support full VSPB on R-Car M3-W, M3-N and E3 Paul Elder
2026-09-18 1:32 ` Laurent Pinchart
2026-09-17 12:04 ` [PATCH 09/10] media: vsp1: Document X5H SoC ID Paul Elder
2026-09-18 1:32 ` Laurent Pinchart
2026-09-17 12:04 ` [PATCH 10/10] media: rcar-fcp: Add R-Car X5H support Paul Elder
2026-09-18 1:35 ` Laurent Pinchart
2026-09-17 12:17 ` [PATCH 00/10] media: rcar-fcp, vsp1: Enable on R-Car X5H Laurent Pinchart
2026-09-18 1:50 ` Laurent Pinchart
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=20260917120938.751AA1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=media-ci@linuxtv.org \
--cc=paul.elder+renesas@ideasonboard.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