From: sashiko-bot@kernel.org
To: "Alexandre Hamamdjian via B4 Relay"
<devnull+azkali.limited.gmail.com@kernel.org>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 2/4] arm64: dts: qcom: sm8550: add labels for thermal zones
Date: Sun, 17 May 2026 13:27:42 +0000 [thread overview]
Message-ID: <20260517132742.CBDEBC2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260517-pocketds-v3-2-d5910c801756@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete implementation: missing labels for almost all CPU thermal zones despite commit message claims.
--
commit 32e1020122d8ab932064f6929e94b9d9f74c8a75
Author: Alexandre Hamamdjian <azkali.limited@gmail.com>
arm64: dts: qcom: sm8550: add labels for thermal zones
This commit adds labels to the cpuss, cpu, and gpuss thermal zones in
the sm8550 device tree. This is intended to allow board files to override
trip points and cooling maps using labels instead of full node paths.
> diff --git a/arch/arm64/boot/dts/qcom/sm8550.dtsi b/arch/arm64/boot/dts/qcom/sm8550.dtsi
> index 912525e9bca6f..a9c678fc9cb2e 100644
> --- a/arch/arm64/boot/dts/qcom/sm8550.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8550.dtsi
[ ... ]
> @@ -6028,7 +6028,7 @@ cpu6_bottom_crit: cpu-critical {
> };
> };
>
> - cpu7-top-thermal {
> + cpu7_top_thermal: cpu7-top-thermal {
> thermal-sensors = <&tsens0 13>;
>
> trips {
The commit message states that labels are added for the cpu thermal zones,
but it looks like only cpu7-top-thermal was updated here.
Were the other CPU thermal zones in this file, such as cpu0-thermal,
cpu1-thermal, cpu3-bottom-thermal, and cpu7-bottom-thermal intentionally
left without labels, or did they get missed during the update?
If they are left out, it seems board files will not be able to extend those
remaining zones using the label override syntax.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260517-pocketds-v3-0-d5910c801756@gmail.com?part=2
next prev parent reply other threads:[~2026-05-17 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 13:14 [PATCH v3 0/4] arm64: qcom: add Ayaneo Pocket DS gaming console Alexandre Hamamdjian via B4 Relay
2026-05-17 13:14 ` [PATCH v3 1/4] dt-bindings: arm: qcom: document the Ayaneo Pocket DS Alexandre Hamamdjian via B4 Relay
2026-05-17 13:23 ` sashiko-bot
2026-05-17 13:14 ` [PATCH v3 2/4] arm64: dts: qcom: sm8550: add labels for thermal zones Alexandre Hamamdjian via B4 Relay
2026-05-17 13:27 ` sashiko-bot [this message]
2026-05-17 20:33 ` Dmitry Baryshkov
2026-05-17 13:14 ` [PATCH v3 3/4] arm64: dts: qcom: add basic devicetree for Ayaneo Pocket DS gaming console Alexandre Hamamdjian via B4 Relay
2026-05-17 13:46 ` sashiko-bot
2026-05-17 20:32 ` Dmitry Baryshkov
2026-05-17 13:14 ` [PATCH v3 4/4] arm64: dts: qcom: sm8550: add UART11 node Alexandre Hamamdjian via B4 Relay
2026-05-17 14:05 ` sashiko-bot
2026-05-17 20:33 ` Dmitry Baryshkov
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=20260517132742.CBDEBC2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+azkali.limited.gmail.com@kernel.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