Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jishnu Prakash" <jishnu.prakash@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 2/4] arm64: dts: qcom: pm8005: Add temp alarm node
Date: Fri, 11 Sep 2026 16:51:39 +0000	[thread overview]
Message-ID: <20260911165139.A63671F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260911-shikra_adc_support-v6-2-e4b2da5cd55c@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The critical trip temperature of 145000 mC exceeds the hardware's maximum Stage 2 shutdown threshold, causing a premature hard-power cut that bypasses OS software shutdown.
--

commit 88b914c28016cf188fecbd155d9b9942de82bce0
Author: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>

arm64: dts: qcom: pm8005: Add temp alarm node
    
This commit adds a temperature alarm node along with a thermal zone used
for PMIC thermal mitigation on the PM8005.
    
> diff --git a/arch/arm64/boot/dts/qcom/pm8005.dtsi b/arch/arm64/boot/dts/qcom/pm8005.dtsi
> index 0f0ab2da83055..ce31a85450200 100644
> --- a/arch/arm64/boot/dts/qcom/pm8005.dtsi
> +++ b/arch/arm64/boot/dts/qcom/pm8005.dtsi
[ ... ]
> +				pm8005_trip1: trip1 {
> +					temperature = <125000>;
> +					hysteresis = <0>;
> +					type = "hot";
> +				};
> +
> +				pm8005_trip2: trip2 {
> +					temperature = <145000>;
> +					hysteresis = <0>;
> +					type = "critical";
> +				};

[Severity: High]
Does setting this temperature to 145000 mC exceed the hardware's maximum
Stage 2 shutdown threshold (typically 125000 mC or 140000 mC depending on the
generation)?

If this threshold is physically unattainable by the hardware without an ADC,
could this force an early, ungraceful hardware power cut before the OS is
able to reach the thermal framework's graceful shutdown procedure?

[ ... ]
>  &spmi_bus {
>  	pm8005_lsid0: pmic@4 {
>  		compatible = "qcom,pm8005", "qcom,spmi-pmic";
> @@ -11,6 +39,13 @@ pm8005_lsid0: pmic@4 {
>  		#address-cells = <1>;
>  		#size-cells = <0>;
>  
> +		pm8005_tz: temp-alarm@2400 {
> +			compatible = "qcom,spmi-temp-alarm";
> +			reg = <0x2400>;
> +			interrupts = <0x4 0x24 0x0 IRQ_TYPE_EDGE_BOTH>;
> +			#thermal-sensor-cells = <0>;
> +		};

[Severity: High]
Because there is no io-channels property defined here, it looks like the
qcom-spmi-temp-alarm driver will have to rely on the PMIC's internal hardware
comparators instead of an ADC.

When the driver attempts to configure the 145000 mC critical trip point from
above, will it find that it exceeds the hardware's maximum threshold, cap it
at the hardware maximum, and leave SHUTDOWN_CTRL1_OVERRIDE_STAGE2 disabled?

If so, would the PMIC abruptly power off when the temperature reaches the
lower Stage 2 hardware threshold? This bypasses the OS thermal framework's
graceful shutdown and can potentially lead to filesystem corruption on
overheating. Should an io-channels property be provided here to properly
delegate the critical trip to software?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260911-shikra_adc_support-v6-0-e4b2da5cd55c@oss.qualcomm.com?part=2

  reply	other threads:[~2026-09-11 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 16:40 [PATCH v6 0/4] arm64: dts: qcom: Add PMIC thermal support for Shikra platforms Jishnu Prakash
2026-09-11 16:40 ` [PATCH v6 1/4] arm64: dts: qcom: pm4125: Add VADC and temp alarm nodes Jishnu Prakash
2026-09-12 15:35   ` Abel Vesa
2026-09-11 16:40 ` [PATCH v6 2/4] arm64: dts: qcom: pm8005: Add temp alarm node Jishnu Prakash
2026-09-11 16:51   ` sashiko-bot [this message]
2026-09-12 15:35   ` Abel Vesa
2026-09-11 16:40 ` [PATCH v6 3/4] arm64: dts: qcom: Add PMIC thermal support for Shikra CQ2390M SoM platform Jishnu Prakash
2026-09-11 16:51   ` sashiko-bot
2026-09-12 15:36   ` Abel Vesa
2026-09-11 16:40 ` [PATCH v6 4/4] arm64: dts: qcom: Add PMIC thermal support for Shikra IQ2390S " Jishnu Prakash
2026-09-11 16:49   ` sashiko-bot
2026-09-12 15:36   ` 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=20260911165139.A63671F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jishnu.prakash@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox