From: Marcel Ziswiler <marcel@ziswiler.com>
To: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] arm: tegra: apalis-tk1: set critical trips
Date: Sat, 10 Feb 2018 02:38:01 +0100 [thread overview]
Message-ID: <20180210013806.28496-2-marcel@ziswiler.com> (raw)
In-Reply-To: <20180210013806.28496-1-marcel@ziswiler.com>
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Set "critical" trip temperatures for cpu, gpu, mem and pllx
thermal zones. These trips can trigger shut down or reset.
Similar to commit 40823f8e267f ("arm: tegra: set critical
trips for Tegra124").
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
---
arch/arm/boot/dts/tegra124-apalis.dtsi | 27 +++------------------------
1 file changed, 3 insertions(+), 24 deletions(-)
diff --git a/arch/arm/boot/dts/tegra124-apalis.dtsi b/arch/arm/boot/dts/tegra124-apalis.dtsi
index 7aef8928e115..be45b6753916 100644
--- a/arch/arm/boot/dts/tegra124-apalis.dtsi
+++ b/arch/arm/boot/dts/tegra124-apalis.dtsi
@@ -2041,53 +2041,32 @@
thermal-zones {
cpu {
trips {
- trip@0 {
+ cpu-shutdown-trip {
temperature = <101000>;
hysteresis = <0>;
type = "critical";
};
};
-
- cooling-maps {
- /*
- * There are currently no cooling maps because
- * there are no cooling devices
- */
- };
};
mem {
trips {
- trip@0 {
+ mem-shutdown-trip {
temperature = <101000>;
hysteresis = <0>;
type = "critical";
};
};
-
- cooling-maps {
- /*
- * There are currently no cooling maps because
- * there are no cooling devices
- */
- };
};
gpu {
trips {
- trip@0 {
+ gpu-shutdown-trip {
temperature = <101000>;
hysteresis = <0>;
type = "critical";
};
};
-
- cooling-maps {
- /*
- * There are currently no cooling maps because
- * there are no cooling devices
- */
- };
};
};
};
--
2.14.3
next prev parent reply other threads:[~2018-02-10 1:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 1:38 [PATCH 0/6] ARM: dts: tegra: apalis-tk1: updates incl. v1.2 hardware support Marcel Ziswiler
2018-02-10 1:38 ` Marcel Ziswiler [this message]
2018-02-10 1:38 ` [PATCH 2/6] ARM: dts: tegra: apalis-tk1: activate pwm pin muxing for pwm3 Marcel Ziswiler
2018-03-08 15:14 ` Thierry Reding
2018-02-10 1:38 ` [PATCH 3/6] ARM: dts: tegra: apalis-tk1: add missing as3722 gpio0 configuration Marcel Ziswiler
2018-02-10 1:38 ` [PATCH 4/6] ARM: dts: tegra: apalis-tk1: hog group for ethernet, pcie, reset gpios Marcel Ziswiler
2018-02-10 1:38 ` [PATCH 5/6] ARM: dts: tegra: apalis-tk1: copyright period, spurious newlines Marcel Ziswiler
2018-02-10 7:07 ` Philippe Ombredanne
2018-02-10 8:40 ` Marcel Ziswiler
2018-02-10 14:48 ` Philippe Ombredanne
2018-02-10 1:38 ` [PATCH 6/6] ARM: dts: tegra: apalis-tk1: support v1.2 hardware revision Marcel Ziswiler
2018-03-08 15:19 ` [PATCH 0/6] ARM: dts: tegra: apalis-tk1: updates incl. v1.2 hardware support 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=20180210013806.28496-2-marcel@ziswiler.com \
--to=marcel@ziswiler.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcel.ziswiler@toradex.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®