From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 0/2] OMAP 2/3 GPIO fixes for idling debounce clocks
Date: Mon, 02 Feb 2009 12:15:27 -0800 [thread overview]
Message-ID: <87ocxkbnog.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1233194282-30057-1-git-send-email-khilman@deeprootsystems.com> (Kevin Hilman's message of "Wed\, 28 Jan 2009 17\:58\:00 -0800")
Kevin Hilman <khilman@deeprootsystems.com> writes:
> [updated since v1: also works for retention/off when idle by
> masking off GPIO clocks in the 'fclks_active' check.]
>
> This series against the current PM branch is to add support for
> auto-disabling GPIO debounce clocks when the system is idle. Without
> this, any platform using the GPIO debounce feature will not go into
> retention since the GPIO debounce clocks are still active.
>
> This is needed particularily on OMAP3EVM which sets up the debounce
> clocks for the touchscreen GPIO.
>
> Kevin Hilman (2):
> OMAP2/3: GPIO: generalize prepare for idle
> OMAP3: GPIO: disable GPIO debounce clocks on idle
>
> arch/arm/mach-omap2/pm24xx.c | 4 ++--
> arch/arm/mach-omap2/pm34xx.c | 14 ++++++++------
> arch/arm/plat-omap/gpio.c | 27 +++++++++++++++++++++------
> arch/arm/plat-omap/include/mach/gpio.h | 4 ++--
> 4 files changed, 33 insertions(+), 16 deletions(-)
Pushing this series to PM branch.
Kevin
prev parent reply other threads:[~2009-02-02 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 1:58 [PATCH v2 0/2] OMAP 2/3 GPIO fixes for idling debounce clocks Kevin Hilman
2009-01-29 1:58 ` [PATCH v2 1/2] OMAP2/3: GPIO: generalize prepare for idle Kevin Hilman
2009-01-29 1:58 ` [PATCH v2 2/2] OMAP3: GPIO: disable GPIO debounce clocks on idle Kevin Hilman
2009-02-02 20:15 ` Kevin Hilman [this message]
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=87ocxkbnog.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 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.