From: Neil Armstrong <neil.armstrong@linaro.org>
To: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>,
sre@kernel.org, hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
linux@roeck-us.net, andersson@kernel.org, konradybcio@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: bryan.odonoghue@linaro.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Lenovo ThinkPad T14s EC thermal monitoring and thermal zone integration
Date: Fri, 3 Jul 2026 12:32:32 +0200 [thread overview]
Message-ID: <5edfa760-b5b1-4f0e-8a14-2a39d2b99090@linaro.org> (raw)
In-Reply-To: <20260701103714.22583-1-daniel.lezcano@oss.qualcomm.com>
On 7/1/26 12:37, Daniel Lezcano wrote:
> Hi,
>
> This series extends the Lenovo ThinkPad T14s embedded controller driver
> with environmental monitoring capabilities and integrates the exposed
> sensors into the Linux thermal framework.
>
> The EC provides access to several platform temperature sensors
> covering the SoC, keyboard area, bottom cover, charging circuitry, QTM
> module and SSD. These sensors are currently used by the firmware for
> thermal management but are not exposed to Linux.
>
> The first patch adds hwmon support for the EC temperature sensors.
>
> The second patch exposes the EC as a thermal sensor provider in the
> device tree and defines thermal zones for the keyboard skin
> temperature and the charging circuitry temperature. This allows the
> generic thermal framework to react to EC-reported temperatures and
> apply standard Linux thermal mitigation policies.
>
> As the EC protocol is not fully decoded, the passive trip points
> get/set actions are missing, so it is not possible to program a
> threshold and receive an interrupt when crossed the way up or
> down. Consequently, the thermal zone related to the charging circuitry
> is polled every two seconds until we can set the trip points in the
> EC.
>
> This series fixes critical thermal issues happening on this platform
> where a kernel compilation, or heavy workloads, lead to a system
> reboot.
>
> Tested on a Lenovo ThinkPad T14s Gen 6 (Snapdragon X Elite).
>
> Thanks,
>
> Daniel
>
> ---
> Changelog:
> v3:
> - Removed event based because trip point are not yet well supported
> - Added an empty line after variable declaration (Ilpo Järvinen)
> - Used MILLIDEGREE_PER_DEGREE from units.h (Ilpo Järvinen)
> - Made switch consistent (Ilpo Järvinen)
> v2:
> - Fixed patch 1 subject prefix
> - Removed the fan information part
> - Added HWMON_T_ALARM
> - Fixed DT change description to reflect what it does really
>
> Daniel Lezcano (2):
> platform: arm64: lenovo-thinkpad-t14s-ec: Add hwmon support for
> temperatures
> arm64: dts: qcom: x1e78100-t14s: Add thermal zones for keyboard skin
> and charging sensors
>
> .../qcom/x1e78100-lenovo-thinkpad-t14s.dtsi | 68 ++++++++-
> drivers/platform/arm64/lenovo-thinkpad-t14s.c | 130 ++++++++++++++++++
> 2 files changed, 197 insertions(+), 1 deletion(-)
>
Tested-by: Neil Armstrong <neil.armstrong@linaro.org> # on T14s OLED
next prev parent reply other threads:[~2026-07-03 10:32 UTC|newest]
Thread overview: 10+ 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
2026-07-02 12:17 ` Konrad Dybcio
2026-07-02 13:35 ` Daniel Lezcano
2026-07-03 10:32 ` Neil Armstrong [this message]
2026-07-03 14:09 ` [PATCH v3 0/2] Lenovo ThinkPad T14s EC thermal monitoring and thermal zone integration Neil Armstrong
2026-07-03 14:11 ` Neil Armstrong
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=5edfa760-b5b1-4f0e-8a14-2a39d2b99090@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
/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