From: Russ Dill <Russ.Dill@ti.com>
To: linux-omap@vger.kernel.org
Cc: devicetree@vger.kernel.org,
Kevin Hilman <khilman@deeprootsystems.com>,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org
Subject: [PATCH v4 3/4] ARM: dts: add AM33XX vdd core opp50 suspend for AM335X GP EVM.
Date: Tue, 13 Aug 2013 15:20:11 -0700 [thread overview]
Message-ID: <1376432412-8509-4-git-send-email-Russ.Dill@ti.com> (raw)
In-Reply-To: <1376432412-8509-1-git-send-email-Russ.Dill@ti.com>
From: Hebbar, Gururaja <gururaja.hebbar@ti.com>
This adds a sleep and wake sequence to set the VDD core voltage to the
OPP50 level, 0.950V. This saves power during suspend. The sequences are
specific to the EVM layout and PMIC, the TPS65910. The sequences
are written out by the Cortex-M3.
Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
Signed-off-by: Russ Dill <Russ.Dill@ti.com>
---
arch/arm/boot/dts/am335x-evm.dts | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index 3aee1a4..81ce169 100644
--- a/arch/arm/boot/dts/am335x-evm.dts
+++ b/arch/arm/boot/dts/am335x-evm.dts
@@ -166,6 +166,16 @@
status = "okay";
clock-frequency = <400000>;
+ /* Set OPP50 (0.95V) for VDD core */
+ sleep_sequence = /bits/ 8 <
+ 0x02 0x2d 0x25 0x1f /* Set VDD2 to 0.95V */
+ >;
+
+ /* Set OPP100 (1.10V) for VDD core */
+ wake_sequence = /bits/ 8 <
+ 0x02 0x2d 0x25 0x2b /* Set VDD2 to 1.1V */
+ >;
+
tps: tps@2d {
reg = <0x2d>;
};
--
1.8.3.2
next prev parent reply other threads:[~2013-08-13 22:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 22:20 [PATCH v4 0/4] ARM: OMAP2+: AM33XX: VDD CORE OPP50 support Russ Dill
2013-08-13 22:20 ` [PATCH v4 1/4] ARM: OMAP2+: AM33XX: I2C Sleep/wake sequence support Russ Dill
2013-08-14 10:18 ` Gururaja Hebbar
2013-08-14 22:34 ` Russ Dill
2013-08-16 7:16 ` Gururaja Hebbar
2013-08-19 5:49 ` Gururaja Hebbar
2013-08-20 16:33 ` Russ Dill
2013-08-21 8:29 ` Gururaja Hebbar
2013-08-13 22:20 ` [PATCH v4 2/4] ARM: dts: add AM33XX vdd core opp50 suspend for Beaglebone Russ Dill
2013-08-14 8:59 ` Gururaja Hebbar
2013-08-14 22:21 ` Russ Dill
2013-08-13 22:20 ` Russ Dill [this message]
2013-08-13 22:20 ` [PATCH v4 4/4] ARM: dts: AM33XX vdd core opp50 suspend for EVM-SK Russ Dill
2013-08-14 13:38 ` [PATCH v4 0/4] ARM: OMAP2+: AM33XX: VDD CORE OPP50 support Jan Lübbe
2013-08-14 22:21 ` Russ Dill
2013-08-15 8:00 ` Jan Lübbe
2013-08-27 22:44 ` Kevin Hilman
2013-08-28 1:05 ` Russ Dill
2013-08-29 11:05 ` Mark Brown
2013-08-29 15:29 ` Kevin Hilman
2013-08-29 15:49 ` Mark Brown
2013-08-29 16:31 ` Russ Dill
2013-08-29 17:30 ` Mark Brown
2013-08-29 17:47 ` Russ Dill
2013-08-29 18:03 ` Mark Brown
2013-08-29 18:28 ` Russ Dill
2013-08-29 15:42 ` Russ Dill
2013-08-29 18:01 ` Mark Brown
2013-08-29 18:25 ` Russ Dill
2013-08-29 19:10 ` Mark Brown
2013-09-03 14:06 ` Russ Dill
2013-09-03 14:39 ` Mark Brown
2013-08-29 15:17 ` Kevin Hilman
2013-08-29 16:10 ` Russ Dill
2013-08-29 19:11 ` Kevin Hilman
2013-08-29 20:09 ` Vaibhav Bedia
2013-08-29 21:33 ` Kevin Hilman
2013-08-30 0:25 ` Russ Dill
2013-08-30 16:06 ` Kevin Hilman
2013-09-03 18:55 ` Russ Dill
2013-09-03 19:07 ` Kevin Hilman
2013-08-30 17:57 ` Vaibhav Bedia
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=1376432412-8509-4-git-send-email-Russ.Dill@ti.com \
--to=russ.dill@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
/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).