All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dipa Ramesh Mantre" <dipa.mantre@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: shikra: Enable CDSP & Modem cooling
Date: Fri, 11 Sep 2026 05:14:31 +0000	[thread overview]
Message-ID: <20260911051431.C37301F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260911-shikra_qmi_tmd-v1-2-96c1cca82f30@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The patch introduces a fatal build failure by including a non-existent device tree bindings header file and referencing undefined macros for the QMI TMD cooling framework.
- [Low] The addition of the `#cooling-cells` property to the remoteproc nodes violates strict Device Tree schema bindings.
--

commit 4b1a1d4f27b1c457bd265f6d0f4a5b333e378019
Author: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>

arm64: dts: qcom: shikra: Enable CDSP & Modem cooling

This commit sets up CDSP and modem cooling by throttling them using the
QMI TMD cooling device framework when they reach high temperatures.

> diff --git a/arch/arm64/boot/dts/qcom/shikra.dtsi b/arch/arm64/boot/dts/qcom/shikra.dtsi
> index c1f06f692f664..55bac1b57cbac 100644
> --- a/arch/arm64/boot/dts/qcom/shikra.dtsi
> +++ b/arch/arm64/boot/dts/qcom/shikra.dtsi
> @@ -10,6 +10,7 @@
>  #include <dt-bindings/interconnect/qcom,icc.h>
>  #include <dt-bindings/interconnect/qcom,osm-l3.h>
>  #include <dt-bindings/dma/qcom-gpi.h>
> +#include <dt-bindings/thermal/qcom,pas.h>

[Severity: Low]
The header file <dt-bindings/thermal/qcom,pas.h> appears to be completely
missing from the tree.

Does this include cause a fatal build failure?

[ ... ]

> @@ -2007,6 +2008,8 @@ remoteproc_mpss: remoteproc@6080000 {
>  			qcom,smem-states = <&modem_smp2p_out 0>;
>  			qcom,smem-state-names = "stop";
>  
> +			#cooling-cells = <3>;

[Severity: Low]
The #cooling-cells property is not documented in the remoteproc schemas.
The qcom,shikra-pas.yaml and qcom,pas-common.yaml bindings specify
unevaluatedProperties: false.

Does adding this property cause make dtbs_check to fail with a schema
validation error?

[ ... ]

> @@ -2047,6 +2050,8 @@ remoteproc_cdsp: remoteproc@b300000 {
>  			qcom,smem-states = <&cdsp_smp2p_out 0>;
>  			qcom,smem-state-names = "stop";
>  
> +			#cooling-cells = <3>;

[Severity: Low]
This seems to add #cooling-cells to the remoteproc_cdsp node as well.

Does this also trigger the same strict DT schema validation failure?

[ ... ]

> @@ -3877,15 +3884,31 @@ trip-point0 {
>  					type = "hot";
>  				};
>  
> -				nsp-critical {
> +				nsp_alert1: nsp-alert1 {
>  					temperature = <115000>;
> +					hysteresis = <5000>;
> +					type = "passive";
> +				};
> +
> +				nsp-critical {
> +					temperature = <118000>;
>  					hysteresis = <0>;
>  					type = "critical";
>  				};
>  			};
> +
> +			cooling-maps {
> +				map0 {
> +					trip = <&nsp_alert1>;
> +					cooling-device = <&remoteproc_cdsp QCOM_TMD_CDSP_SW
> +							 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;

[Severity: Low]
The <dt-bindings/thermal/qcom,pas.h> header is missing, which leaves macros
like QCOM_TMD_CDSP_SW, QCOM_TMD_PA, and QCOM_TMD_MODEM undefined.

Will this line lead to a fatal device tree compiler error?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260911-shikra_qmi_tmd-v1-0-96c1cca82f30@oss.qualcomm.com?part=2

      reply	other threads:[~2026-09-11  5:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  5:03 [PATCH 0/2] Add QMI TMD based cooling support for the Shikra CDSP and Modem Dipa Ramesh Mantre
2026-09-11  5:03 ` [PATCH 1/2] remoteproc: qcom_q6v5_pas: Add QMI TMD cooling support for Shikra Dipa Ramesh Mantre
2026-09-11  5:09   ` sashiko-bot
2026-09-11  5:03 ` [PATCH 2/2] arm64: dts: qcom: shikra: Enable CDSP & Modem cooling Dipa Ramesh Mantre
2026-09-11  5:14   ` 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=20260911051431.C37301F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dipa.mantre@oss.qualcomm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.