Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Shawn Guo" <shengchao.guo@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 8/8] arm64: dts: qcom: Add device tree for SA8797P Ride board
Date: Tue, 19 May 2026 07:35:58 +0000	[thread overview]
Message-ID: <20260519073559.5E042C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519063505.883379-9-shengchao.guo@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Flawed thermal zone configurations with incorrect types, descending order, and identical duplicate trip points.
--

commit feec939ce542144572175512accde079d1c6829f
Author: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>

arm64: dts: qcom: Add device tree for SA8797P Ride board

This commit adds the initial device tree for the Qualcomm SA8797P Ride
reference board. It configures UART ports, enables UFS storage, and
defines various thermal zones using the SCMI sensor protocol.

> diff --git a/arch/arm64/boot/dts/qcom/sa8797p-ride.dts b/arch/arm64/boot/dts/qcom/sa8797p-ride.dts
> new file mode 100644
> index 0000000000000..2eab2c6fc173d
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sa8797p-ride.dts

[ ... ]

> +	pm_kobra_thermal: pm-a-die-thermal {
> +		polling-delay-passive = <100>;
> +		polling-delay = <0>;
> +		thermal-sensors = <&scmi23_sensor 3>;
> +
> +		trips {
> +			trip0 {
> +				temperature = <135000>;
> +				hysteresis = <5000>;
> +				type = "passive";
> +			};
> +
> +			pm_kobra_trip1: trip1 {
> +				temperature = <115000>;
> +				hysteresis = <5000>;
> +				type = "passive";
> +			};
> +		};
> +	};

Should trip0 be configured as an emergency hardware shutdown trip point
instead of passive, considering the high 135C temperature limit?

Also, does the thermal framework expect these trip points to be defined in
ascending order of temperature rather than descending?

[ ... ]

> +	pm_kai_ufs_thermal: ufs-thermal {
> +		polling-delay-passive = <0>;
> +		polling-delay = <0>;
> +		thermal-sensors = <&scmi23_sensor 0>;
> +
> +		trips {
> +			trip0 {
> +				temperature = <125000>;
> +				hysteresis = <5000>;
> +				type = "passive";
> +			};
> +
> +			trip1 {
> +				temperature = <125000>;
> +				hysteresis = <5000>;
> +				type = "passive";
> +			};
> +		};
> +	};

Are these duplicate trip points intentional? Both trip0 and trip1 are defined
with the exact same temperature, hysteresis, and passive type.

Is it possible that trip1 was intended to have a higher temperature and
serve as a different type of trip point?

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

      reply	other threads:[~2026-05-19  7:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  6:34 [PATCH v2 0/8] Add initial device trees for Nord SA8797P Shawn Guo
2026-05-19  6:34 ` [PATCH v2 1/8] dt-bindings: arm: qcom,ids: Add SoC ID " Shawn Guo
2026-05-19  6:34 ` [PATCH v2 2/8] soc: qcom: socinfo: " Shawn Guo
2026-05-19  6:35 ` [PATCH v2 3/8] soc: qcom: socinfo: Add PMIC PMAU0102 Shawn Guo
2026-05-19  6:35 ` [PATCH v2 4/8] dt-bindings: crypto: qcom,inline-crypto-engine: Document Nord ICE Shawn Guo
2026-05-19 10:50   ` Harshal Dev
2026-05-19  6:35 ` [PATCH v2 5/8] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-05-19  7:04   ` sashiko-bot
2026-05-19  6:35 ` [PATCH v2 6/8] arm64: dts: qcom: Add device tree for Nord SA8797P SoC Shawn Guo
2026-05-19  7:16   ` sashiko-bot
2026-05-19  6:35 ` [PATCH v2 7/8] dt-bindings: arm: qcom: Document SA8797P Ride board Shawn Guo
2026-05-19  7:28   ` sashiko-bot
2026-05-19  6:35 ` [PATCH v2 8/8] arm64: dts: qcom: Add device tree for " Shawn Guo
2026-05-19  7:35   ` 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=20260519073559.5E042C2BCB3@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