public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: PM branch updates: 3430sdp and omap3evm results
Date: Tue, 27 Jan 2009 10:16:06 -0800	[thread overview]
Message-ID: <87fxj4ty1l.fsf@deeprootsystems.com> (raw)

Hello,

I've updated the PM branch with a couple of fixes that get it working
on the 3430SDP.

For it to work on the SDP, you need the latest u-boot from the
omapzoom u-boot tree[1].  This fixes the problems I was having with
the D2D clockdomain remaining active or hanging upon clock disable.

For omap3evm, it is not hitting retention because it uses the GPIO
debounce feature for the touchscreen and the GPIO debounce clocks are
not disabled in idle or suspend.  As a temporary hack, you can test
the patch below[2] which simply doesn't call the gpio debounce
functions for the touchscreen.  In the meantime, I'm working on a
patch to disable the debounce clocks on idle.

Kevin

[1] git://git.omapzoom.org/repo/u-boot.git

[2]
da7df18bc7f5648ac7fe6e674065ca5899ff8d3d
 arch/arm/mach-omap2/board-omap3evm.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/mach-omap2/board-omap3evm.c b/arch/arm/mach-omap2/board-omap3evm.c
index 6fbbe95..18a07b5 100644
--- a/arch/arm/mach-omap2/board-omap3evm.c
+++ b/arch/arm/mach-omap2/board-omap3evm.c
@@ -176,8 +176,8 @@ static void ads7846_dev_init(void)
 
 	gpio_direction_input(OMAP3_EVM_TS_GPIO);
 
-	omap_set_gpio_debounce(OMAP3_EVM_TS_GPIO, 1);
-	omap_set_gpio_debounce_time(OMAP3_EVM_TS_GPIO, 0xa);
+/* 	omap_set_gpio_debounce(OMAP3_EVM_TS_GPIO, 1); */
+/* 	omap_set_gpio_debounce_time(OMAP3_EVM_TS_GPIO, 0xa); */
 }
 

             reply	other threads:[~2009-01-27 18:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 18:16 Kevin Hilman [this message]
2009-01-27 19:29 ` PM branch updates: 3430sdp and omap3evm results Koen Kooi
2009-01-27 19:52   ` Kevin Hilman
2009-01-27 20:00     ` Koen Kooi
2009-02-01 14:05 ` Ramesh Gupta Guntha
2009-02-04  5:34   ` Ramesh Gupta Guntha
2009-02-04  5:42     ` Kevin Hilman
2009-02-04  5:44       ` Ramesh Gupta Guntha
2009-02-04  6:10         ` Kevin Hilman
2009-02-04  6:24           ` Ramesh Gupta Guntha
2009-02-05 14:34             ` Kevin Hilman
2009-02-05 14:50               ` Ramesh Gupta Guntha
2009-02-10 21:01                 ` Ramesh Gupta Guntha
2009-02-10 22:28                   ` Kevin Hilman
2009-02-12  0:32                     ` Tony Lindgren
2009-02-12  1:30                       ` Ramesh Gupta Guntha
2009-02-12 12:58                         ` Ramesh Gupta Guntha
2009-02-04  6:34           ` jouni.hogander

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=87fxj4ty1l.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --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