From: sashiko-bot@kernel.org
To: "Daniel Lezcano" <daniel.lezcano@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: x1e78100-thinkpad-t14s: Add thermal zones for PMICs
Date: Tue, 22 Sep 2026 18:31:34 +0000 [thread overview]
Message-ID: <20260922183135.18EA61F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260922181818.5503-1-daniel.lezcano@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] dts: missing #thermal-sensor-cells on pmk8550_vadc breaks thermal zones
--
commit 2a17ffae5a77fa31a5cd42aff532d2ad2eb0c1c2
Author: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
arm64: dts: qcom: x1e78100-thinkpad-t14s: Add thermal zones for PMICs
This commit adds thermal zones for the ThinkPad T14s and describes the
board temperature sensors exposed through the PMK8550 VADC. It includes
passive and shutdown thermal zones for the keyboard area and back cover,
along with monitoring-only zones.
> diff --git a/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dts b/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dts
> index 5cc6a63d1ef66..9407868864ad3 100644
> --- a/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dts
> +++ b/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dts
> @@ -10,6 +10,117 @@ / {
> compatible = "lenovo,thinkpad-t14s-lcd", "lenovo,thinkpad-t14s",
> "qcom,x1e78100", "qcom,x1e80100";
>
> + thermal-zones {
> + soc-thermal {
> + thermal-sensors = <&pmk8550_vadc ADC5_GEN3_AMUX1_GPIO_100K_PU(1)>;
> + };
> +
> + keyboard-thermal {
> + critical-action = "shutdown";
> + polling-delay-passive = <500>;
> +
> + thermal-sensors = <&pmk8550_vadc ADC5_GEN3_AMUX2_GPIO_100K_PU(1)>;
[Severity: High]
Will this thermal zone fail to parse and register at runtime due to the target
pmk8550_vadc node missing the #thermal-sensor-cells property?
Without these thermal zones registering successfully, the system might lack
the intended thermal throttling for the keyboard constraint and the 73°C
shutdown trip, risking hardware overheating under load.
[ ... ]
> @@ -58,3 +170,33 @@ edp_bl_pwm: edp-bl-pwm-state {
> &pmk8550_pwm {
> status = "okay";
> };
> +
> +&pmk8550_vadc {
> + channel@144 {
> + qcom,adc-tm;
> + };
[Severity: High]
Should this extension of pmk8550_vadc include #thermal-sensor-cells = <1>; ?
Since the base definition in hamoa-pmics.dtsi omits it, it appears to be
required here for the framework to parse it as a valid thermal sensor provider.
Otherwise, of_parse_phandle_with_args() returns -EINVAL unconditionally at
boot when evaluating the thermal-sensors properties above.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922181818.5503-1-daniel.lezcano@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-09-22 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 18:18 [PATCH] arm64: dts: qcom: x1e78100-thinkpad-t14s: Add thermal zones for PMICs Daniel Lezcano
2026-09-22 18:31 ` sashiko-bot [this message]
2026-09-22 18:42 ` Daniel Lezcano
2026-09-23 9:08 ` Konrad Dybcio
2026-09-23 19:07 ` johannes.goede
2026-09-23 19:43 ` Hans de Goede
2026-09-29 9:31 ` Stephan Gerhold
2026-09-29 9:59 ` 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=20260922183135.18EA61F00893@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=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