All of lore.kernel.org
 help / color / mirror / Atom feed
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 v1 07/13] ARM: tegra: acer-a500: Reduce thermal throttling hysteresis to 0.2C
Date: Thu, 21 Jan 2021 21:23:02 +0300	[thread overview]
Message-ID: <20210121182308.16080-8-digetx@gmail.com> (raw)
In-Reply-To: <20210121182308.16080-1-digetx@gmail.com>

The 2C hysteresis is a bit too high, although CPU never gets hot on A500.
Nevertheless, let's reduce thermal throttling hysteresis to 0.2C, which is
a much more reasonable value.

Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
 arch/arm/boot/dts/tegra20-acer-a500-picasso.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts b/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
index 8531abf329c6..64a303cc5395 100644
--- a/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
+++ b/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
@@ -1058,7 +1058,7 @@ trips {
 				trip0: cpu-alert0 {
 					/* start throttling at 50C */
 					temperature = <50000>;
-					hysteresis = <3000>;
+					hysteresis = <200>;
 					type = "passive";
 				};
 
-- 
2.29.2


  parent reply	other threads:[~2021-01-21 18:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 18:22 [PATCH v1 00/13] NVIDIA Tegra ARM32 device-tree improvements Dmitry Osipenko
2021-01-21 18:22 ` [PATCH v1 01/13] ARM: tegra: ventana: Support CPU and Core voltage scaling Dmitry Osipenko
2021-01-21 18:22 ` [PATCH v1 02/13] ARM: tegra: ventana: Support CPU thermal throttling Dmitry Osipenko
2021-01-21 18:22 ` [PATCH v1 03/13] ARM: tegra: cardhu: Support CPU frequency and voltage scaling on all board variants Dmitry Osipenko
2021-01-21 18:22 ` [PATCH v1 04/13] ARM: tegra: cardhu: Support CPU thermal throttling Dmitry Osipenko
2021-01-21 18:23 ` [PATCH v1 05/13] ARM: tegra: paz00: Enable full voltage scaling ranges for CPU and Core domains Dmitry Osipenko
2021-01-21 18:23 ` [PATCH v1 06/13] ARM: tegra: acer-a500: Enable core voltage scaling Dmitry Osipenko
2021-01-21 18:23 ` Dmitry Osipenko [this message]
2021-01-21 18:23 ` [PATCH v1 08/13] ARM: tegra: acer-a500: Specify all CPU cores as cooling devices Dmitry Osipenko
2021-01-21 18:23 ` [PATCH v1 09/13] ARM: tegra: acer-a500: Rename avdd to vdda of touchscreen node Dmitry Osipenko
2021-01-22 20:14   ` Dmitry Osipenko
2021-01-21 18:23 ` [PATCH v1 10/13] ARM: tegra: nexus7: Specify all CPU cores as cooling devices Dmitry Osipenko
2021-01-21 18:23 ` [PATCH v1 11/13] ARM: tegra: ouya: " Dmitry Osipenko
2021-01-21 18:23 ` [PATCH v1 12/13] ARM: tegra: Specify CPU suspend OPP in device-tree Dmitry Osipenko
2021-01-21 18:23 ` [PATCH v1 13/13] ARM: tegra: Specify memory " Dmitry Osipenko

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=20210121182308.16080-8-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.