From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Gaurav Kohli <gaurav.kohli@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>,
Amit Kucheria <amit.kucheria@oss.qualcomm.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Konrad Dybcio <konradybcio@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 Meethalavalappu Pallikunhi
<manaf.pallikunhi@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v3 1/8] dt-bindings: remoteproc: qcom,pas: add thermal mitigation properties
Date: Wed, 24 Jun 2026 17:56:13 +0200 [thread overview]
Message-ID: <ae0ec05e-607b-4022-a006-2eb1a283144d@oss.qualcomm.com> (raw)
In-Reply-To: <5b0f1f39-ddaa-4a2e-ab29-34aacc9ff672@kernel.org>
On 6/24/26 12:42, Krzysztof Kozlowski wrote:
[ ... ]
> Therefore I still do not see the need of tmd-names. You know the name of
> cooling device, because you have strict one-to-one mapping.
There is one remote proc with one or multiple cooling devices attached.
We describe those in the remoteproc node with the tmd-names.
Anyway, we should be able to list the tmd names in the driver itself if
we ensure a consistency with the index by defining them in a shared
header eg. include/dt-bindings/firmware/qcom,cdsp.h
#define HAMOA_TMD_CDSP_SW 0
#define HAMOA_TMD_CDSP_HW 1
#define HAMOA_TMD_CP0UV_RESTRICTION_COLD 2
In the driver:
struct tmd_name {
const char *name;
int id;
bool disabled;
};
static struct tmd_name tmd_names[] = {
{ .name = "cdsp_sw", HAMOA_TMD_CDSP_SW },
{ .name = "cdsp_hw", HAMOA_TMD_CDSP_HW, .disabled = true },
{ .name = "cpuv_restriction_cold", HAMOA_TMD_CP0UV_RESTRICTION_COLD,
.disabled = true },
};
...
for (int i = 0; i < ARRAY_SIZE(tmd_names); i++) {
if (tmd_names[i].disabled)
continue;
devm_cooling_of_device_register(rprocdev,
tmd_names[i].name, tmd_names[i].id, ...);
}
In the device tree:
cooling-maps = <&rproc HAMOA_TMD_CDSP_SW min max>;
I think that is somehow what Konrad and Dmitry were suggesting
Does it sound better ?
next prev parent reply other threads:[~2026-06-24 15:56 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:22 [PATCH v3 0/8] Add support for Qualcomm remoteproc subsystem cooling Gaurav Kohli
2026-06-09 10:22 ` [PATCH v3 1/8] dt-bindings: remoteproc: qcom,pas: add thermal mitigation properties Gaurav Kohli
2026-06-09 10:47 ` Dmitry Baryshkov
2026-06-10 12:02 ` Gaurav Kohli
2026-06-10 7:31 ` Krzysztof Kozlowski
2026-06-11 11:12 ` Gaurav Kohli
2026-06-11 12:23 ` Krzysztof Kozlowski
2026-06-12 13:52 ` Gaurav Kohli
2026-06-13 7:41 ` Krzysztof Kozlowski
2026-06-13 11:05 ` Gaurav Kohli
2026-06-15 5:03 ` Krzysztof Kozlowski
2026-06-15 10:34 ` Daniel Lezcano
2026-06-15 12:12 ` Gaurav Kohli
2026-06-15 12:30 ` Daniel Lezcano
2026-06-15 14:11 ` Dmitry Baryshkov
2026-06-15 14:33 ` Daniel Lezcano
2026-06-15 15:14 ` Dmitry Baryshkov
2026-06-15 15:33 ` Daniel Lezcano
2026-06-15 22:15 ` Dmitry Baryshkov
2026-06-17 12:32 ` Konrad Dybcio
2026-06-19 12:16 ` Daniel Lezcano
2026-06-16 4:21 ` Krzysztof Kozlowski
2026-06-18 7:17 ` Daniel Lezcano
2026-06-24 10:42 ` Krzysztof Kozlowski
2026-06-24 15:56 ` Daniel Lezcano [this message]
2026-06-25 6:48 ` Krzysztof Kozlowski
2026-06-25 7:51 ` Daniel Lezcano
2026-06-29 14:31 ` Gaurav Kohli
2026-06-09 10:22 ` [PATCH v3 2/8] soc: qcom: Add support for QMI TMD cooling devices Gaurav Kohli
2026-06-09 11:30 ` Dmitry Baryshkov
2026-06-09 12:08 ` Daniel Lezcano
2026-06-10 13:42 ` Dmitry Baryshkov
2026-06-10 14:15 ` Daniel Lezcano
2026-06-11 10:53 ` Gaurav Kohli
2026-06-11 22:50 ` Dmitry Baryshkov
2026-06-09 10:22 ` [PATCH v3 3/8] remoteproc: qcom: pas: register TMD thermal " Gaurav Kohli
2026-06-09 11:05 ` Dmitry Baryshkov
2026-06-09 12:03 ` Konrad Dybcio
2026-06-11 4:45 ` Gaurav Kohli
2026-06-11 20:34 ` Dmitry Baryshkov
2026-06-09 10:22 ` [PATCH v3 4/8] arm64: dts: qcom: kodiak: Enable CDSP & Modem cooling Gaurav Kohli
2026-06-09 10:57 ` Dmitry Baryshkov
2026-06-15 5:32 ` Gaurav Kohli
2026-06-15 15:25 ` Dmitry Baryshkov
2026-06-29 14:43 ` Gaurav Kohli
2026-06-09 10:23 ` [PATCH v3 5/8] arm64: dts: qcom: lemans: Enable CDSP cooling Gaurav Kohli
2026-06-09 10:23 ` [PATCH v3 6/8] arm64: dts: qcom: talos: " Gaurav Kohli
2026-06-09 10:23 ` [PATCH v3 7/8] arm64: dts: qcom: monaco: " Gaurav Kohli
2026-06-09 10:23 ` [PATCH v3 8/8] arm64: dts: qcom: hamoa: " Gaurav Kohli
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=ae0ec05e-607b-4022-a006-2eb1a283144d@oss.qualcomm.com \
--to=daniel.lezcano@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=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gaurav.kohli@oss.qualcomm.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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=manaf.pallikunhi@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
/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®