From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Nicolas Chauvet <kwizart@gmail.com>,
Matt Merhar <mattmerhar@protonmail.com>,
Peter Geis <pgwipeout@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 08/14] ARM: tegra: acer-a500: Specify all CPU cores as cooling devices
Date: Tue, 2 Mar 2021 15:09:57 +0300 [thread overview]
Message-ID: <20210302121003.15058-9-digetx@gmail.com> (raw)
In-Reply-To: <20210302121003.15058-1-digetx@gmail.com>
If CPU0 is unplugged the cooling device can not rebind to CPU1. And if
CPU0 is plugged in again, the cooling device may fail to initialize.
If the CPUs are mapped with the physical CPU0 to Linux numbering
CPU1, the cooling device mapping will fail.
Hence specify all CPU cores as a cooling devices in the device-tree.
Suggested-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
arch/arm/boot/dts/tegra20-acer-a500-picasso.dts | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts b/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
index 64a303cc5395..8a98e4a9d994 100644
--- a/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
+++ b/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
@@ -841,9 +841,10 @@ cpu0: cpu@0 {
#cooling-cells = <2>;
};
- cpu@1 {
+ cpu1: cpu@1 {
cpu-supply = <&vdd_cpu>;
operating-points-v2 = <&cpu0_opp_table>;
+ #cooling-cells = <2>;
};
};
@@ -1073,7 +1074,8 @@ trip1: cpu-crit {
cooling-maps {
map0 {
trip = <&trip0>;
- cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
+ cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
+ <&cpu1 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
};
};
};
--
2.29.2
next prev parent reply other threads:[~2021-03-02 13:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 12:09 [PATCH v3 00/14] NVIDIA Tegra ARM32 device-tree improvements Dmitry Osipenko
2021-03-02 12:09 ` [PATCH v3 01/14] ARM: tegra: ventana: Support CPU and Core voltage scaling Dmitry Osipenko
2021-03-02 12:09 ` [PATCH v3 02/14] ARM: tegra: ventana: Support CPU thermal throttling Dmitry Osipenko
2021-03-02 12:09 ` [PATCH v3 03/14] ARM: tegra: cardhu: Support CPU frequency and voltage scaling on all board variants Dmitry Osipenko
2021-03-02 12:09 ` [PATCH v3 04/14] ARM: tegra: cardhu: Support CPU thermal throttling Dmitry Osipenko
2021-03-02 12:09 ` [PATCH v3 05/14] ARM: tegra: paz00: Enable full voltage scaling ranges for CPU and Core domains Dmitry Osipenko
2021-03-02 12:09 ` [PATCH v3 06/14] ARM: tegra: acer-a500: Enable core voltage scaling Dmitry Osipenko
2021-03-02 12:09 ` [PATCH v3 07/14] ARM: tegra: acer-a500: Reduce thermal throttling hysteresis to 0.2C Dmitry Osipenko
2021-03-02 12:09 ` Dmitry Osipenko [this message]
2021-03-02 12:09 ` [PATCH v3 09/14] ARM: tegra: acer-a500: Rename avdd to vdda of touchscreen node Dmitry Osipenko
2021-03-24 15:11 ` Thierry Reding
2021-03-24 15:24 ` Dmitry Osipenko
2021-03-02 12:09 ` [PATCH v3 10/14] ARM: tegra: nexus7: Specify all CPU cores as cooling devices Dmitry Osipenko
2021-03-02 12:10 ` [PATCH v3 11/14] ARM: tegra: ouya: " Dmitry Osipenko
2021-03-02 12:10 ` [PATCH v3 12/14] ARM: tegra: Specify CPU suspend OPP in device-tree Dmitry Osipenko
2021-03-02 12:10 ` [PATCH v3 13/14] ARM: tegra: Specify memory " Dmitry Osipenko
2021-03-02 12:10 ` [PATCH v3 14/14] ARM: tegra: Specify tps65911 as wakeup source Dmitry Osipenko
2021-03-24 15:12 ` [PATCH v3 00/14] NVIDIA Tegra ARM32 device-tree improvements 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=20210302121003.15058-9-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=kwizart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=pgwipeout@gmail.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).