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 v2 05/13] ARM: tegra: paz00: Enable full voltage scaling ranges for CPU and Core domains
Date: Fri, 22 Jan 2021 23:24:49 +0300 [thread overview]
Message-ID: <20210122202457.13326-6-digetx@gmail.com> (raw)
In-Reply-To: <20210122202457.13326-1-digetx@gmail.com>
Enable full voltage scaling ranges for CPU and Core power domains.
Tested-by: Nicolas Chauvet <kwizart@gmail.com>
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
arch/arm/boot/dts/tegra20-paz00.dts | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/arch/arm/boot/dts/tegra20-paz00.dts b/arch/arm/boot/dts/tegra20-paz00.dts
index 7e49112cd9a1..940a9f31cd86 100644
--- a/arch/arm/boot/dts/tegra20-paz00.dts
+++ b/arch/arm/boot/dts/tegra20-paz00.dts
@@ -387,10 +387,10 @@ sys_reg: sys {
core_vdd_reg: sm0 {
regulator-name = "+1.2vs_sm0,vdd_core";
- regulator-min-microvolt = <1200000>;
- regulator-max-microvolt = <1225000>;
+ regulator-min-microvolt = <950000>;
+ regulator-max-microvolt = <1300000>;
regulator-coupled-with = <&rtc_vdd_reg &cpu_vdd_reg>;
- regulator-coupled-max-spread = <170000 450000>;
+ regulator-coupled-max-spread = <170000 550000>;
regulator-always-on;
nvidia,tegra-core-regulator;
@@ -401,7 +401,7 @@ cpu_vdd_reg: sm1 {
regulator-min-microvolt = <750000>;
regulator-max-microvolt = <1100000>;
regulator-coupled-with = <&core_vdd_reg &rtc_vdd_reg>;
- regulator-coupled-max-spread = <450000 450000>;
+ regulator-coupled-max-spread = <550000 550000>;
regulator-always-on;
nvidia,tegra-cpu-regulator;
@@ -425,10 +425,10 @@ ldo1 {
rtc_vdd_reg: ldo2 {
regulator-name = "+1.2vs_ldo2,vdd_rtc";
- regulator-min-microvolt = <1200000>;
- regulator-max-microvolt = <1225000>;
+ regulator-min-microvolt = <950000>;
+ regulator-max-microvolt = <1300000>;
regulator-coupled-with = <&core_vdd_reg &cpu_vdd_reg>;
- regulator-coupled-max-spread = <170000 450000>;
+ regulator-coupled-max-spread = <170000 550000>;
regulator-always-on;
nvidia,tegra-rtc-regulator;
--
2.29.2
next prev parent reply other threads:[~2021-01-22 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 20:24 [PATCH v2 00/13] NVIDIA Tegra ARM32 device-tree improvements Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 01/13] ARM: tegra: ventana: Support CPU and Core voltage scaling Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 02/13] ARM: tegra: ventana: Support CPU thermal throttling Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 03/13] ARM: tegra: cardhu: Support CPU frequency and voltage scaling on all board variants Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 04/13] ARM: tegra: cardhu: Support CPU thermal throttling Dmitry Osipenko
2021-01-22 20:24 ` Dmitry Osipenko [this message]
2021-01-22 20:24 ` [PATCH v2 06/13] ARM: tegra: acer-a500: Enable core voltage scaling Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 07/13] ARM: tegra: acer-a500: Reduce thermal throttling hysteresis to 0.2C Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 08/13] ARM: tegra: acer-a500: Specify all CPU cores as cooling devices Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 09/13] ARM: tegra: acer-a500: Rename avdd to vdda of touchscreen node Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 10/13] ARM: tegra: nexus7: Specify all CPU cores as cooling devices Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 11/13] ARM: tegra: ouya: " Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 12/13] ARM: tegra: Specify CPU suspend OPP in device-tree Dmitry Osipenko
2021-01-22 20:24 ` [PATCH v2 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=20210122202457.13326-6-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).