Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Daniel Lezcano" <daniel.lezcano@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	linux-hwmon@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: x1e78100-t14s: Add thermal zones for keyboard skin and charging sensors
Date: Mon, 06 Jul 2026 16:16:00 +0000	[thread overview]
Message-ID: <20260706161601.22FE31F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260706160830.17698-3-daniel.lezcano@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch adds the `#thermal-sensor-cells = <1>;` property to the `embedded-controller@28` node without a corresponding update to the device tree binding document (`lenovo,thinkpad-t14s-ec.yaml`), violating the DT schema.
--

commit 6785b707e0b11ce8dd5032f0c96a9debef8c413f
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 Lenovo ThinkPad T14s embedded controller as a thermal
sensor provider and adds thermal zones for the keyboard skin and charging
sensors in the device tree. It allows the thermal framework to apply CPU
throttling when the charging circuitry exceeds passive thresholds.

> 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..ed5ba3a428a8d 100644
> --- a/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi
> +++ b/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi
> @@ -979,7 +979,7 @@ &i2c6 {
>  
>  	status = "okay";
>  
> -	embedded-controller@28 {
> +	ec: embedded-controller@28 {
>  		compatible = "lenovo,thinkpad-t14s-ec";
>  		reg = <0x28>;
>  
> @@ -988,6 +988,8 @@ embedded-controller@28 {
>  		pinctrl-0 = <&ec_int_n_default>;
>  		pinctrl-names = "default";
>  
> +		#thermal-sensor-cells = <1>;

[Severity: Low]
Does adding this property to the embedded-controller@28 node without a
corresponding update to the binding schema cause make dtbs_check to emit
validation warnings?

Since the lenovo,thinkpad-t14s-ec.yaml binding does not define this property
and uses additionalProperties: false, it seems that adding it here will
trigger a warning. Should the schema be updated to allow this property?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260706160830.17698-1-daniel.lezcano@oss.qualcomm.com?part=2

      reply	other threads:[~2026-07-06 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 16:08 [PATCH v4 0/2] Lenovo ThinkPad T14s EC thermal monitoring and thermal zone integration Daniel Lezcano
2026-07-06 16:08 ` [PATCH v4 1/2] platform: arm64: lenovo-thinkpad-t14s-ec: Add hwmon support for temperatures Daniel Lezcano
2026-07-06 16:12   ` Ilpo Järvinen
2026-07-06 16:14   ` sashiko-bot
2026-07-06 16:08 ` [PATCH v4 2/2] arm64: dts: qcom: x1e78100-t14s: Add thermal zones for keyboard skin and charging sensors Daniel Lezcano
2026-07-06 16:16   ` sashiko-bot [this message]

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=20260706161601.22FE31F000E9@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