From: Thierry Reding <thierry.reding@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>
Cc: linux-tegra@vger.kernel.org
Subject: [PATCH 2/3] arm64: Fix up cooling map names on Tegra186
Date: Wed, 2 Sep 2026 16:42:39 +0200 [thread overview]
Message-ID: <20260902144240.766879-2-thierry.reding@kernel.org> (raw)
In-Reply-To: <20260902144240.766879-1-thierry.reding@kernel.org>
From: Thierry Reding <treding@nvidia.com>
Cooling map nodes should be prefixed with map-, so make the necessary
adjustments on Tegra186.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
.../boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts b/arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts
index d9aafe053112..4b2fa1a49f05 100644
--- a/arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts
+++ b/arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts
@@ -1176,22 +1176,22 @@ cpu_trip_passive: passive {
};
cooling-maps {
- cpu-critical {
+ map-critical {
cooling-device = <&fan 3 3>;
trip = <&cpu_trip_critical>;
};
- cpu-hot {
+ map-hot {
cooling-device = <&fan 2 2>;
trip = <&cpu_trip_hot>;
};
- cpu-active {
+ map-active {
cooling-device = <&fan 1 1>;
trip = <&cpu_trip_active>;
};
- cpu-passive {
+ map-passive {
cooling-device = <&fan 0 0>;
trip = <&cpu_trip_passive>;
};
--
2.55.0
next prev parent reply other threads:[~2026-09-02 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 14:42 [PATCH 1/3] arm64: tegra: Fix up cooling map names on Tegra194 Thierry Reding
2026-09-02 14:42 ` Thierry Reding [this message]
2026-09-02 14:42 ` [PATCH 3/3] arm64: Fix up cooling map names on Tegra210 Thierry Reding
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=20260902144240.766879-2-thierry.reding@kernel.org \
--to=thierry.reding@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.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