From: sashiko-bot@kernel.org
To: "Anvesh Jain P" <anvesh.p@oss.qualcomm.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: glymur: Add EC thermal zones
Date: Mon, 28 Sep 2026 06:51:55 +0000 [thread overview]
Message-ID: <20260928065156.218CE1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260928-ec_thermistor_support-v1-3-d9c1bae4cd0d@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: qcom: thermal zone nodes violate thermal-zones schema
--
commit 5002150e61d17adad9a02df5206f78ef229da8ab
Author: Anvesh Jain P <anvesh.p@oss.qualcomm.com>
arm64: dts: qcom: glymur: Add EC thermal zones
This commit adds support for back cover, keyboard, and SoC thermal zones
through temperature sensors hosted on the EC for Glymur and Mahua CRDs.
> diff --git a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> index e27c697e31702..571c98124a406 100644
> --- a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> +++ b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
[ ... ]
> @@ -955,6 +957,47 @@ right_tweeter: speaker@0,1 {
> };
> };
>
> +&thermal_zones {
> + ec-back-cover {
[Severity: Low]
Does this node name violate the thermal-zones.yaml schema? The schema
requires thermal zone nodes to have a -thermal suffix (matching the regex
^[a-zA-Z][a-zA-Z0-9\-]{1,10}-thermal$).
Additionally, trivially appending -thermal to ec-back-cover yields a
21-character string. The schema limits the prefix to 10 characters, and
the kernel enforces a THERMAL_NAME_LENGTH limit of 20 bytes (including
NUL). Should the prefix be shortened to comply with these limits?
> + polling-delay = <10000>;
> + thermal-sensors = <&ec 2>;
> +
> + trips {
[ ... ]
> + };
> + };
> + };
> +
> + ec-keyboard {
[Severity: Low]
Does this node name also need the -thermal suffix to pass dtbs_check
validation against the thermal-zones schema?
> + polling-delay = <10000>;
> + thermal-sensors = <&ec 1>;
> +
> + trips {
[ ... ]
> + };
> + };
> + };
> +
> + ec-soc {
[Severity: Low]
Does this node name also need the -thermal suffix to pass dtbs_check
validation?
> + polling-delay = <10000>;
> + thermal-sensors = <&ec 0>;
> +
> + trips {
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260928-ec_thermistor_support-v1-0-d9c1bae4cd0d@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-09-28 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 6:36 [PATCH 0/3] platform: arm64: qcom-hamoa-ec: Add thermistor support Anvesh Jain P
2026-09-28 6:36 ` [PATCH 1/3] dt-bindings: embedded-controller: qcom,hamoa-crd-ec: Add thermal sensors Anvesh Jain P
2026-09-28 6:48 ` sashiko-bot
2026-09-28 6:36 ` [PATCH 2/3] platform: arm64: qcom-hamoa-ec: Add thermistor sensors Anvesh Jain P
2026-09-29 7:35 ` Ilpo Järvinen
2026-09-30 5:02 ` Anvesh Jain P
2026-09-28 6:36 ` [PATCH 3/3] arm64: dts: qcom: glymur: Add EC thermal zones Anvesh Jain P
2026-09-28 6:51 ` sashiko-bot [this message]
2026-09-29 8:56 ` Krzysztof Kozlowski
2026-09-29 10:07 ` Anvesh Jain P
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=20260928065156.218CE1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=anvesh.p@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--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