From: Wei Ni <wni@nvidia.com>
To: edubezval@gmail.com, thierry.reding@gmail.com,
robh+dt@kernel.org, rui.zhang@intel.com
Cc: MLongnecker@nvidia.com, swarren@wwwdotorg.org,
mikko.perttunen@kapsi.fi, linux-tegra@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Wei Ni <wni@nvidia.com>
Subject: [PATCH v5 10/11] arm64: tegra: set critical trips for Tegra210
Date: Wed, 11 May 2016 18:20:25 +0800 [thread overview]
Message-ID: <1462962026-19653-11-git-send-email-wni@nvidia.com> (raw)
In-Reply-To: <1462962026-19653-1-git-send-email-wni@nvidia.com>
Set general "critical" trip temperatures for cpu, gpu, mem and pllx
thermal zones on Tegra210, these trips can trigger shut down or reset.
Signed-off-by: Wei Ni <wni@nvidia.com>
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 60 ++++++++++++++++++++++++++++++++
1 file changed, 60 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
index 97d75149a1ac..e55589c8a561 100644
--- a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
@@ -825,6 +825,21 @@
thermal-sensors =
<&soctherm TEGRA124_SOCTHERM_SENSOR_CPU>;
+
+ trips {
+ cpu-shutdown-trip {
+ temperature = <102500>;
+ hysteresis = <0>;
+ type = "critical";
+ };
+ };
+
+ cooling-maps {
+ /*
+ * There are currently no cooling maps,
+ * because there are no cooling devices.
+ */
+ };
};
mem {
polling-delay-passive = <0>;
@@ -832,6 +847,21 @@
thermal-sensors =
<&soctherm TEGRA124_SOCTHERM_SENSOR_MEM>;
+
+ trips {
+ mem-shutdown-trip {
+ temperature = <103000>;
+ hysteresis = <0>;
+ type = "critical";
+ };
+ };
+
+ cooling-maps {
+ /*
+ * There are currently no cooling maps,
+ * because there are no cooling devices.
+ */
+ };
};
gpu {
polling-delay-passive = <1000>;
@@ -839,6 +869,21 @@
thermal-sensors =
<&soctherm TEGRA124_SOCTHERM_SENSOR_GPU>;
+
+ trips {
+ gpu-shutdown-trip {
+ temperature = <103000>;
+ hysteresis = <0>;
+ type = "critical";
+ };
+ };
+
+ cooling-maps {
+ /*
+ * There are currently no cooling maps,
+ * because there are no cooling devices.
+ */
+ };
};
pllx {
polling-delay-passive = <0>;
@@ -846,6 +891,21 @@
thermal-sensors =
<&soctherm TEGRA124_SOCTHERM_SENSOR_PLLX>;
+
+ trips {
+ pllx-shutdown-trip {
+ temperature = <103000>;
+ hysteresis = <0>;
+ type = "critical";
+ };
+ };
+
+ cooling-maps {
+ /*
+ * There are currently no cooling maps,
+ * because there are no cooling devices.
+ */
+ };
};
};
};
--
1.9.1
next prev parent reply other threads:[~2016-05-11 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 10:20 [PATCH v5 00/11] Add HW throttle for Tegra soctherm Wei Ni
2016-05-11 10:20 ` [PATCH v5 03/11] thermal: tegra: add hw-throttle for Tegra132 Wei Ni
2016-05-11 10:20 ` [PATCH v5 04/11] arm: tegra: set critical trips for Tegra124 Wei Ni
2016-05-11 10:20 ` [PATCH v5 05/11] arm: tegra: set hot " Wei Ni
2016-05-11 10:20 ` [PATCH v5 07/11] arm64: tegra: set critical trips for Tegra132 Wei Ni
2016-05-11 10:20 ` [PATCH v5 08/11] arm64: tegra: set hot " Wei Ni
2016-05-11 10:20 ` [PATCH v5 09/11] arm64: tegra: add soctherm node for Tegra210 Wei Ni
2016-05-11 10:20 ` Wei Ni [this message]
2016-05-11 10:20 ` [PATCH v5 11/11] arm64: tegra: set hot trips " Wei Ni
[not found] ` <1462962026-19653-1-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-11 10:20 ` [PATCH v5 01/11] of: Add bindings of hw throttle for Tegra soctherm Wei Ni
2016-05-16 15:01 ` Rob Herring
2016-05-11 10:20 ` [PATCH v5 02/11] thermal: tegra: add hw-throttle function Wei Ni
2016-05-11 10:20 ` [PATCH v5 06/11] arm64: tegra: use tegra132-soctherm for Tegra132 Wei Ni
2016-05-26 9:42 ` [PATCH v5 00/11] Add HW throttle for Tegra soctherm Wei Ni
2016-08-19 7:15 ` Zhang Rui
[not found] ` <1471590924.2691.34.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-08-31 3:07 ` Wei Ni
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=1462962026-19653-11-git-send-email-wni@nvidia.com \
--to=wni@nvidia.com \
--cc=MLongnecker@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mikko.perttunen@kapsi.fi \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=swarren@wwwdotorg.org \
--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).