Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Shawn Guo" <shengchao.guo@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v13 1/6] arm64: dts: qcom: Add device tree for Nord SoC series
Date: Fri, 28 Aug 2026 04:02:12 +0000	[thread overview]
Message-ID: <20260828040213.4B19F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260828034958.3165-2-shengchao.guo@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing critical thermal trip points and cooling maps in all thermal zones, preventing OS-level emergency shutdown and thermal mitigation.
--

commit deb196841a808ec3881552d5d1a8344597819e47
Author: Shawn Guo <shengchao.guo@oss.qualcomm.com>

arm64: dts: qcom: Add device tree for Nord SoC series

Add base device tree include (nord.dtsi) for the Nord SoC series
describing the core hardware components.

> diff --git a/arch/arm64/boot/dts/qcom/nord.dtsi b/arch/arm64/boot/dts/qcom/nord.dtsi
> new file mode 100644
> index 0000000000000..e0496fd40c308
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/nord.dtsi
[ ... ]
> +		cpu-0-0-0-thermal {
> +			polling-delay-passive = <0>;
> +			polling-delay = <0>;
> +			thermal-sensors = <&tsens0 1>;
> +
> +			trips {
> +				trip-point0 {
> +					temperature = <105000>;
> +					hysteresis = <10000>;
> +					type = "passive";
> +				};
> +
> +				trip-point1 {
> +					temperature = <125000>;
> +					hysteresis = <10000>;
> +					type = "passive";
> +				};
> +			};
> +		};

[Severity: High]
Is it intended that this thermal zone, as well as the others defined in this
file, lacks a critical trip point?

Without a critical trip point, the OS will not be able to trigger an emergency
shutdown if temperatures exceed safe limits. Additionally, the defined passive
trip points lack corresponding cooling-maps, meaning no thermal mitigation
(such as CPU throttling) will occur when these thresholds are reached.

Should critical trip points and appropriate cooling maps be added to ensure the
OS can properly manage hardware temperatures?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260828034958.3165-1-shengchao.guo@oss.qualcomm.com?part=1

  reply	other threads:[~2026-08-28  4:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  3:49 [PATCH v13 0/6] Add initial device trees for Nord platform Shawn Guo
2026-08-28  3:49 ` [PATCH v13 1/6] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-08-28  4:02   ` sashiko-bot [this message]
2026-08-28  3:49 ` [PATCH v13 2/6] arm64: dts: qcom: Add device tree for Nord GearVM variant Shawn Guo
2026-08-28  4:00   ` sashiko-bot
2026-08-28  3:49 ` [PATCH v13 3/6] arm64: dts: qcom: Add device tree for Nord Embedded variant Shawn Guo
2026-08-28  3:49 ` [PATCH v13 4/6] dt-bindings: arm: qcom: Document Nord reference boards Shawn Guo
2026-08-28  4:03   ` sashiko-bot
2026-08-28  3:49 ` [PATCH v13 5/6] arm64: dts: qcom: Add device tree for Nord Ride board Shawn Guo
2026-08-28  9:08   ` Abel Vesa
2026-08-28  3:49 ` [PATCH v13 6/6] arm64: dts: qcom: Add device tree for Nord RRD board Shawn Guo
2026-08-28  9:09   ` Abel Vesa

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=20260828040213.4B19F1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=shengchao.guo@oss.qualcomm.com \
    /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