From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@booyaka.com>
Cc: Jouni Hogander <jouni.hogander@nokia.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3: GPIO: Enable debounce clock only when debounce is enabled v3.
Date: Thu, 25 Sep 2008 13:28:09 +0300 [thread overview]
Message-ID: <20080925102808.GH5222@atomide.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0809160656360.21341@utopia.booyaka.com>
* Paul Walmsley <paul@booyaka.com> [080916 16:02]:
> On Tue, 16 Sep 2008, Jouni Hogander wrote:
>
> > This patch changes gpio "driver" to enable debounce clock for
> > gpio-bank only when debounce is enabled for some gpio in that bank.
> >
> > Gpio functional clocks are also renamed in clock tree, gpioX_fck ->
> > gpioX_dbck.
> >
> > This patch triggers problem with gpio wake-up and Omap3. Gpios in PER
> > domain aren't capable to generate wake-up if PER domain is in sleep
> > state. For this iopad wake-up should be used and needed pad
> > configuration should be done. Enabling iopad wake-up for gpio pads is
> > left for bootloader or omap mux configuration in kernel.
> >
> > Signed-off-by: Jouni Hogander <jouni.hogander@nokia.com>
>
> Acked-by: Paul Walmsley <paul@pwsan.com>
Pushing today.
Tony
prev parent reply other threads:[~2008-09-25 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 10:51 [RFC] OMAP3: GPIO: Enable debounce clock only when debounce is enabled Jouni Hogander
2008-09-12 11:11 ` Daniel Stone
2008-09-12 14:34 ` Paul Walmsley
2008-09-15 8:52 ` [PATCH] " Jouni Hogander
2008-09-16 10:58 ` Kevin Hilman
2008-09-16 12:16 ` [PATCH] OMAP3: GPIO: Enable debounce clock only when debounce is enabled v2 Jouni Hogander
2008-09-16 12:19 ` Paul Walmsley
2008-09-16 12:32 ` Högander Jouni
2008-09-16 12:36 ` Paul Walmsley
2008-09-16 12:51 ` [PATCH] OMAP3: GPIO: Enable debounce clock only when debounce is enabled v3 Jouni Hogander
2008-09-16 12:59 ` Paul Walmsley
2008-09-25 10:28 ` Tony Lindgren [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=20080925102808.GH5222@atomide.com \
--to=tony@atomide.com \
--cc=jouni.hogander@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@booyaka.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