From: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>,
Amit Kucheria <amit.kucheria@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-hardening@vger.kernel.org,
manaf.pallikunhi@oss.qualcomm.com
Subject: Re: [PATCH v5 3/9] remoteproc: qcom: pas: add support for TMD thermal cooling devices
Date: Thu, 23 Jul 2026 20:05:05 +0530 [thread overview]
Message-ID: <3e52b76b-9ecb-4c6f-b6c2-a9a2245dc376@oss.qualcomm.com> (raw)
In-Reply-To: <vxmb3padun4hydx3g7r7gecpeawoslc7djpaaxjl3o5bq5n5ip@nf5djjaelfy3>
On 7/22/2026 4:37 AM, Dmitry Baryshkov wrote:
> On Tue, Jul 21, 2026 at 11:59:00AM +0530, Gaurav Kohli wrote:
>> Register Thermal Mitigation Devices (TMDs) for PAS-managed remote
>> processors to enable thermal throttling through QMI.
>>
>> This allows the thermal framework to request mitigation when remote
>> subsystems such as modem and CDSP contribute to thermal pressure.
>>
>> Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
>> ---
>> drivers/remoteproc/Kconfig | 1 +
>> drivers/remoteproc/qcom_q6v5_pas.c | 90 +++++++++++++++++++++++++++++++++++++-
>> 2 files changed, 90 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
>> index 65befdbfa5f7..f7c02edf395f 100644
>> --- a/drivers/remoteproc/Kconfig
>> +++ b/drivers/remoteproc/Kconfig
>> @@ -229,6 +229,7 @@ config QCOM_Q6V5_PAS
>> select QCOM_PIL_INFO
>> select QCOM_MDT_LOADER
>> select QCOM_Q6V5_COMMON
>> + select QCOM_QMI_TMD
>
> Sashiko warned here about the missing NET dependencies.
thanks for review, will fix this.
>
>> select QCOM_RPROC_COMMON
>> select QCOM_SCM
>> select QCOM_PAS
>> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
>> index 25599d728208..dc5be2c030cf 100644
>> --- a/drivers/remoteproc/qcom_q6v5_pas.c
>> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
>> @@ -5,6 +5,7 @@
>> * Copyright (C) 2016 Linaro Ltd
>> * Copyright (C) 2014 Sony Mobile Communications AB
>> * Copyright (c) 2012-2013, The Linux Foundation. All rights reserved.
>> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
>> */
>>
>> #include <linux/clk.h>
>> @@ -26,8 +27,10 @@
>> #include <linux/regulator/consumer.h>
>> #include <linux/remoteproc.h>
>> #include <linux/soc/qcom/mdt_loader.h>
>> +#include <linux/soc/qcom/qmi_tmd.h>
>> #include <linux/soc/qcom/smem.h>
>> #include <linux/soc/qcom/smem_state.h>
>> +#include <dt-bindings/thermal/qcom,qmi-tmd.h>
>>
>> #include "qcom_common.h"
>> #include "qcom_pil_info.h"
>> @@ -38,6 +41,16 @@
>>
>> #define MAX_ASSIGN_COUNT 3
>>
>> +/**
>> + * struct tmd_name - TMD device name to cooling-device index mapping
>> + * @name: TMD device name
>> + * @id: Cooling-device index used as #cooling-cells cell 0 in DT
>> + */
>> +struct tmd_name {
>> + const char *name;
>> + int id;
>> +};
>> +
>> struct qcom_pas_data {
>> int crash_reason_smem;
>> const char *firmware_name;
>> @@ -58,6 +71,10 @@ struct qcom_pas_data {
>> int ssctl_id;
>> unsigned int smem_host_id;
>>
>> + unsigned int tmd_instance_id;
>> + const struct tmd_name *tmd_name;
>> + int num_tmd;
>> +
>> int region_assign_idx;
>> int region_assign_count;
>> bool region_assign_shared;
>> @@ -122,6 +139,8 @@ struct qcom_pas {
>>
>> struct qcom_pas_context *pas_ctx;
>> struct qcom_pas_context *dtb_pas_ctx;
>> +
>> + struct qmi_tmd_client *tmd_inst;
>> };
>>
>> static void qcom_pas_segment_dump(struct rproc *rproc,
>> @@ -798,6 +817,64 @@ static void qcom_pas_unassign_memory_region(struct qcom_pas *pas)
>> }
>> }
>>
>> +static int qcom_pas_setup_tmd(struct qcom_pas *pas, const struct qcom_pas_data *desc)
>> +{
>> + struct qmi_tmd_client *tmd_inst;
>> + const struct tmd_name *tmd;
>> + const char **tmd_names;
>> + int i, ret;
>> +
>> + if (!device_property_present(pas->dev, "#cooling-cells"))
>> + return 0;
>> +
>> + if (!desc->tmd_name || desc->num_tmd == 0)
>> + return 0;
>> +
>> + tmd_names = devm_kcalloc(pas->dev, desc->num_tmd,
>> + sizeof(*tmd_names), GFP_KERNEL);
>> + if (!tmd_names)
>> + return -ENOMEM;
>> +
>> + for (i = 0; i < desc->num_tmd; i++) {
>> + tmd = &desc->tmd_name[i];
>> +
>> + if (tmd->id < 0 || tmd->id >= desc->num_tmd) {
>
> The < 0 check is totally redundant.
Ack, this is redundant only.
>
> For the second check, currently the driver will set num_tmd to
> ARRAY_SIZE(desc->tmds), which makes second part either redundant or
> invalid. I assume that here you want to compare to some maximum TMD
> number to be supported rather than a fixed ARRAY_SIZE().
This is just a defensive check to prevent mistakes in the static mapping
table. The current mappings use dense IDs starting from 0, so
desc->num_tmd matches the valid ID range today.
>
>> + dev_err(pas->dev, "Invalid TMD id %d for '%s'\n",
>> + tmd->id, tmd->name);
>> + return -EINVAL;
>> + }
>> +
>> + if (tmd_names[tmd->id]) {
>> + dev_err(pas->dev, "Duplicate TMD id %d for '%s'\n",
>> + tmd->id, tmd->name);
>> + return -EINVAL;
>> + }
>> +
>> + tmd_names[tmd->id] = tmd->name;
>> + }
>> +
>> + for (i = 0; i < desc->num_tmd; i++) {
>> + if (!tmd_names[i]) {
>> + dev_err(pas->dev, "Missing TMD mapping for id %d\n", i);
>> + return -EINVAL;
>> + }
>> + }
>> +
>> + tmd_inst = qmi_tmd_init(pas->dev, desc->tmd_instance_id, tmd_names,
>> + desc->num_tmd);
>
> And this makes it even more strange. Can there be holes in the
> tmd_names? Can platform omit some of the TMDs? Assumingly yes, this
> is not correct (nor is devm_kcalloc).
thanks for review.
For example, if the static table contains:
tmd1 -> id 0
tmd2 -> id 1
tmd3 -> id 2
but firmware reports only tmd1 and tmd3, then cooling devices are
registered only for IDs 0 and 2. No cooling device is registered for
tmd2, so the corresponding DT cooling-device binding will not happen.
The devm_kcalloc() is still needed because qmi_tmd_init() expects an
indexed name array matching the DT cooling-device IDs. The current
static mapping assumes those IDs are dense, so there are no holes in the
mapping array itself.
>
>> + if (IS_ERR(tmd_inst)) {
>> + ret = PTR_ERR(tmd_inst);
>> + if (ret == -ENODEV)
>> + return 0;
>> +
>> + return ret;
>> + }
>> +
>> + pas->tmd_inst = tmd_inst;
>> +
>> + return 0;
>> +}
>> +
>> static int qcom_pas_probe(struct platform_device *pdev)
>> {
>> const struct qcom_pas_data *desc;
>> @@ -925,16 +1002,24 @@ static int qcom_pas_probe(struct platform_device *pdev)
>> if (desc->early_boot)
>> pas->rproc->state = RPROC_DETACHED;
>>
>> - ret = rproc_add(rproc);
>> + ret = qcom_pas_setup_tmd(pas, desc);
>> if (ret)
>> goto remove_ssr_sysmon;
>>
>> + ret = rproc_add(rproc);
>> + if (ret)
>> + goto remove_setup_tmd;
>> +
>> node = of_get_compatible_child(pdev->dev.of_node, "qcom,bam-dmux");
>> pas->bam_dmux = of_platform_device_create(node, NULL, &pdev->dev);
>> of_node_put(node);
>>
>> return 0;
>>
>> +remove_setup_tmd:
>> + if (pas->tmd_inst)
>> + qmi_tmd_exit(pas->tmd_inst);
>> +
>> remove_ssr_sysmon:
>> qcom_remove_ssr_subdev(rproc, &pas->ssr_subdev);
>> qcom_remove_sysmon_subdev(pas->sysmon);
>> @@ -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);
>>
>> qcom_q6v5_deinit(&pas->q6v5);
>>
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2026-07-23 14:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 6:28 [PATCH v5 0/9] Add support for Qualcomm remoteproc subsystem cooling Gaurav Kohli
2026-07-21 6:28 ` [PATCH v5 1/9] dt-bindings: remoteproc: qcom,pas: add #cooling-cells property Gaurav Kohli
2026-07-22 7:06 ` Krzysztof Kozlowski
2026-07-22 13:38 ` Gaurav Kohli
2026-07-23 7:22 ` Krzysztof Kozlowski
2026-07-21 6:28 ` [PATCH v5 2/9] soc: qcom: Add QMI TMD support for remote thermal mitigation Gaurav Kohli
2026-07-21 6:29 ` [PATCH v5 3/9] remoteproc: qcom: pas: add support for TMD thermal cooling devices Gaurav Kohli
2026-07-21 23:07 ` Dmitry Baryshkov
2026-07-23 14:35 ` Gaurav Kohli [this message]
2026-07-21 6:29 ` [PATCH v5 4/9] remoteproc: qcom_q6v5_pas: enable QMI TMD cooling support Gaurav Kohli
2026-07-21 6:29 ` [PATCH v5 5/9] arm64: dts: qcom: kodiak: Enable CDSP & Modem cooling Gaurav Kohli
2026-07-21 23:11 ` Dmitry Baryshkov
2026-07-22 13:32 ` Gaurav Kohli
2026-07-21 6:29 ` [PATCH v5 6/9] arm64: dts: qcom: lemans: Enable CDSP cooling Gaurav Kohli
2026-07-21 23:12 ` Dmitry Baryshkov
2026-07-21 6:29 ` [PATCH v5 7/9] arm64: dts: qcom: talos: " Gaurav Kohli
2026-07-21 23:12 ` Dmitry Baryshkov
2026-07-21 6:29 ` [PATCH v5 8/9] arm64: dts: qcom: monaco: " Gaurav Kohli
2026-07-21 23:12 ` Dmitry Baryshkov
2026-07-21 6:29 ` [PATCH v5 9/9] arm64: dts: qcom: hamoa: " Gaurav Kohli
2026-07-21 23:13 ` Dmitry Baryshkov
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=3e52b76b-9ecb-4c6f-b6c2-a9a2245dc376@oss.qualcomm.com \
--to=gaurav.kohli@oss.qualcomm.com \
--cc=amit.kucheria@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=daniel.lezcano@kernel.org \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=manaf.pallikunhi@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.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
all inboxes | Powered by JetHome®