From: sashiko-bot@kernel.org
To: "Daniel Lezcano" <daniel.lezcano@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org,
linux-hwmon@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: x1e78100-t14s: Add thermal zones for keyboard skin and charging sensors
Date: Wed, 01 Jul 2026 10:47:03 +0000 [thread overview]
Message-ID: <20260701104703.D7CBD1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260701103714.22583-3-daniel.lezcano@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The DT thermal zones are completely non-functional because the backing EC driver does not register its sensors with the thermal framework. The driver (`drivers/platform/arm64/lenovo-thinkpad-t14s.c`) registers a hwmon device using `devm_hwmon_device_register_with_info()` but fails to include the `HWMON_C_REGISTER_TZ` attribute under a `hwmon_chip` channel, nor does it explicitly call `devm_thermal_of_zone_register()`. The hwmon core requires `HWMON_C_REGISTER_TZ` to automatically register thermal zones. Consequently, the DT thermal zones remain permanently unbound, and the CPU thermal throttling described in the commit will not execute.
--
commit 7064bd8ea5ff8a561ac7494d4e760b120e4d6d03
Author: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
arm64: dts: qcom: x1e78100-t14s: Add thermal zones for keyboard skin and charging sensors
This commit exposes the embedded controller temperature sensors as thermal
zones in the device tree for the Lenovo ThinkPad T14s. It maps the charging
thermal zone to CPU cooling devices, allowing the generic thermal framework
to apply throttling when temperatures exceed the passive threshold.
> diff --git a/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi b/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi
> index 5d49df41be02a..a19a363da9ed5 100644
> --- a/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi
> +++ b/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi
[ ... ]
> @@ -1729,3 +1731,67 @@ &usb_mp_qmpphy1 {
>
> status = "okay";
> };
> +
> +&thermal_zones {
> + ec-keyboard-thermal {
> + polling-delay = <5000>;
> + polling-delay-passive = <1000>;
> +
> + thermal-sensors = <&ec 1>;
[Severity: High]
Will these thermal zones successfully bind to the embedded controller?
Looking at the underlying driver in
drivers/platform/arm64/lenovo-thinkpad-t14s.c, it registers a hwmon device
using devm_hwmon_device_register_with_info() but does not appear to include
the HWMON_C_REGISTER_TZ attribute under a hwmon_chip channel. It also doesn't
seem to explicitly call devm_thermal_of_zone_register().
Without the HWMON_C_REGISTER_TZ attribute, the hwmon core will not
automatically register these thermal zones. Does this mean the DT thermal
zones remain permanently unbound, preventing the CPU thermal throttling
described in the commit message from actually executing?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260701103714.22583-1-daniel.lezcano@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-07-01 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 10:37 [PATCH v3 0/2] Lenovo ThinkPad T14s EC thermal monitoring and thermal zone integration Daniel Lezcano
2026-07-01 10:37 ` [PATCH v3 1/2] platform: arm64: lenovo-thinkpad-t14s-ec: Add hwmon support for temperatures Daniel Lezcano
2026-07-01 10:51 ` sashiko-bot
2026-07-01 10:37 ` [PATCH v3 2/2] arm64: dts: qcom: x1e78100-t14s: Add thermal zones for keyboard skin and charging sensors Daniel Lezcano
2026-07-01 10:47 ` sashiko-bot [this message]
2026-07-02 12:17 ` Konrad Dybcio
2026-07-02 13:35 ` Daniel Lezcano
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=20260701104703.D7CBD1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.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