From: Kevin Hilman <khilman@ti.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap@vger.kernel.org
Subject: Re: GPIO debounce problems on 3.2
Date: Wed, 01 Feb 2012 07:30:49 -0800 [thread overview]
Message-ID: <87wr86fu52.fsf@ti.com> (raw)
In-Reply-To: <CANOLnOMmcztNH+fUzrQxjK5nVVEaAtLi=7ww+dPm0AXEv09qUA@mail.gmail.com> (Grazvydas Ignotas's message of "Wed, 1 Feb 2012 13:46:46 +0200")
Grazvydas Ignotas <notasas@gmail.com> writes:
> On Wed, Feb 1, 2012 at 8:06 AM, Paul Walmsley <paul@pwsan.com> wrote:
>> On Tue, 31 Jan 2012, Paul Walmsley wrote:
>>
>>> Well, whether it's in or out of idle, I'll bet the DEBOUNCENABLE
>>> bits are still set to 1 while the debounce clock is off :-(
>>
>> Along these lines, you might try patching omap2_gpio_prepare_for_idle() to
>> turn off the DEBOUNCENABLE bits?
>
> Yes that helps. I guess I'll carry this in pandora tree, at least
> we'll have debounce while more demanding programs/games are running.
Care to share the patch? It might be worth merging until we have a full
solution.
> Don't know how it's all working for Kevin though..
Now I'm not so sure either...
At first I thought it was because I was getting IO ring wakeups, but
using vanilla 3.2, MPU, CORE & PER are staying on due to the (broken)
UART constraint, so I'm getting module-level wakeups, but haven't dug
into why.
Kevin
next prev parent reply other threads:[~2012-02-01 15:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 22:57 GPIO debounce problems on 3.2 Grazvydas Ignotas
2012-01-30 19:36 ` Kevin Hilman
2012-01-30 22:07 ` Grazvydas Ignotas
2012-01-30 23:18 ` Kevin Hilman
2012-01-30 23:34 ` Paul Walmsley
2012-01-31 0:22 ` Kevin Hilman
2012-01-31 1:00 ` Grazvydas Ignotas
2012-01-31 0:56 ` Grazvydas Ignotas
2012-01-31 1:48 ` Paul Walmsley
2012-01-31 11:39 ` Grazvydas Ignotas
2012-01-31 21:40 ` Grazvydas Ignotas
2012-02-01 6:02 ` Paul Walmsley
2012-02-01 6:06 ` Paul Walmsley
2012-02-01 11:46 ` Grazvydas Ignotas
2012-02-01 15:30 ` Kevin Hilman [this message]
2012-02-01 22:33 ` Grazvydas Ignotas
2012-02-01 18:41 ` Paul Walmsley
2012-05-04 21:17 ` Grazvydas Ignotas
2012-02-01 5:47 ` Paul Walmsley
2012-02-01 6:21 ` NeilBrown
2012-02-01 6:58 ` Paul Walmsley
2012-01-31 1:49 ` Paul Walmsley
2012-01-31 6:13 ` Paul Walmsley
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=87wr86fu52.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=paul@pwsan.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 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.