From: sashiko-bot@kernel.org
To: "Ronald Claveau" <linux-kernel-dev@aliel.fr>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
linux-amlogic@lists.infradead.org, neil.armstrong@linaro.org
Subject: Re: [PATCH 1/2] dt-bindings: thermal: amlogic: describe bus clock for t7-thermal
Date: Wed, 23 Sep 2026 12:00:31 +0000 [thread overview]
Message-ID: <20260923120031.88A2D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260923-fix-t7-thermal-clock-v1-1-7d4c4682f182@aliel.fr>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] dt-bindings: thermal: amlogic: ABI breakage by prepending new bus clock
--
commit 9cad8324bf204ceb98e53aadbfac54a0b8d04da6
Author: Ronald Claveau <linux-kernel-dev@aliel.fr>
dt-bindings: thermal: amlogic: describe bus clock for t7-thermal
This commit updates the amlogic thermal device tree binding to support a
secondary "bus" clock required by the t7-thermal sensor. It adds the
"clock-names" property to distinguish between the "bus" and "core" clocks
and requires both for the t7-thermal compatible.
> diff --git a/Documentation/devicetree/bindings/thermal/amlogic,thermal.yaml b/Documentation/devicetree/bindings/thermal/amlogic,thermal.yaml
> index 8cfa44dcda58c..e72cb39ac635d 100644
> --- a/Documentation/devicetree/bindings/thermal/amlogic,thermal.yaml
> +++ b/Documentation/devicetree/bindings/thermal/amlogic,thermal.yaml
> @@ -32,7 +32,15 @@ properties:
> maxItems: 1
>
> clocks:
> - maxItems: 1
> + minItems: 1
> + items:
> + - description: Bus clock, gates register access to the sensor.
> + - description: Functional clock of the temperature sensor, shared between sensors.
> +
> + clock-names:
> + items:
> + - const: bus
> + - const: core
[Severity: Critical]
Does prepending the new "bus" clock at index 0 introduce an ABI regression?
Since older kernels use devm_clk_get(dev, NULL) to unconditionally fetch
the clock at index 0 (as seen in drivers/thermal/amlogic_thermal.c:
amlogic_thermal_probe()), updating the device tree to match this new schema
will cause those older kernels to fetch the "bus" clock instead of the
functional "core" clock.
This will leave the functional clock disabled and prevent the thermal sensor
from operating. While a later patch in this series updates the driver to use
devm_clk_bulk_get_all(), the device tree schema remains broken for older
kernels.
Would it be better to append the new "bus" clock at index 1 to avoid
breaking backward and forward compatibility?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923-fix-t7-thermal-clock-v1-0-7d4c4682f182@aliel.fr?part=1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-09-23 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 11:51 [PATCH 0/2] Add bus clock for t7-thermal sensor Ronald Claveau via B4 Relay
2026-09-23 11:51 ` [PATCH 1/2] dt-bindings: thermal: amlogic: describe bus clock for t7-thermal Ronald Claveau via B4 Relay
2026-09-23 12:00 ` sashiko-bot [this message]
2026-09-23 12:02 ` Krzysztof Kozlowski
2026-09-23 12:17 ` linux-kernel-dev
2026-09-23 11:51 ` [PATCH 2/2] thermal/drivers/amlogic: switch to clk_bulk API to support multiple clocks Ronald Claveau via B4 Relay
2026-09-23 12:00 ` 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=20260923120031.88A2D1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel-dev@aliel.fr \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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
all inboxes | Powered by JetHome®