All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Gaurav Kohli" <gaurav.kohli@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 3/9] remoteproc: qcom: pas: add support for TMD thermal cooling devices
Date: Mon, 27 Jul 2026 14:37:51 +0000	[thread overview]
Message-ID: <20260727143751.8E6C51F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260727-b4-qmi-tmd-v6-3-973cd3a226af@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incorrect teardown order of the TMD client relative to the remoteproc device in `qcom_pas_remove()`.
--

--- Patch [3]: [PATCH v6 3/9] remoteproc: qcom: pas: add support for TMD thermal cooling devices ---
commit 96a80a2d7479048c20fb270197f15552907de3de
Author: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>

remoteproc: qcom: pas: add support for TMD thermal cooling devices

This commit registers Thermal Mitigation Devices (TMDs) for PAS-managed
remote processors to enable thermal throttling through QMI.

> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
> index 25599d7282083..07336a2d75f73 100644
> --- a/drivers/remoteproc/qcom_q6v5_pas.c
> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
[ ... ]
> @@ -960,6 +1045,9 @@ static void qcom_pas_remove(struct platform_device *pdev)
>  	if (pas->bam_dmux)
>  		of_platform_device_destroy(&pas->bam_dmux->dev, NULL);
>  
> +	if (pas->tmd_inst)
> +		qmi_tmd_exit(pas->tmd_inst);
> +
>  	rproc_del(pas->rproc);

[Severity: Low]
Does this sequence unregister the thermal mitigation cooling device in the
wrong order?

Looking at qcom_pas_probe(), qcom_pas_setup_tmd() is called before rproc_add().
Should qmi_tmd_exit() be called after rproc_del() in qcom_pas_remove()
to maintain strict reverse-initialization ordering?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260727-b4-qmi-tmd-v6-0-973cd3a226af@oss.qualcomm.com?part=3

  reply	other threads:[~2026-07-27 14:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 14:22 [PATCH v6 0/9] Add support for Qualcomm remoteproc subsystem cooling Gaurav Kohli
2026-07-27 14:22 ` [PATCH v6 1/9] dt-bindings: remoteproc: qcom,pas: add #cooling-cells property Gaurav Kohli
2026-07-27 14:22 ` [PATCH v6 2/9] soc: qcom: Add QMI TMD support for remote thermal mitigation Gaurav Kohli
2026-07-27 14:40   ` sashiko-bot
2026-07-27 14:22 ` [PATCH v6 3/9] remoteproc: qcom: pas: add support for TMD thermal cooling devices Gaurav Kohli
2026-07-27 14:37   ` sashiko-bot [this message]
2026-07-27 21:55   ` Daniel Lezcano
2026-07-27 14:22 ` [PATCH v6 4/9] remoteproc: qcom_q6v5_pas: enable QMI TMD cooling support Gaurav Kohli
2026-07-27 14:22 ` [PATCH v6 5/9] arm64: dts: qcom: kodiak: Enable CDSP & Modem cooling Gaurav Kohli
2026-07-27 14:22 ` [PATCH v6 6/9] arm64: dts: qcom: lemans: Enable CDSP cooling Gaurav Kohli
2026-07-27 14:22 ` [PATCH v6 7/9] arm64: dts: qcom: talos: " Gaurav Kohli
2026-07-27 14:22 ` [PATCH v6 8/9] arm64: dts: qcom: monaco: " Gaurav Kohli
2026-07-27 14:22 ` [PATCH v6 9/9] arm64: dts: qcom: hamoa: " Gaurav Kohli
2026-07-27 14:36   ` sashiko-bot

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=20260727143751.8E6C51F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gaurav.kohli@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.