From: Kevin Hilman <khilman@ti.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-omap@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@stericsson.com>
Subject: Re: [PATCH] gpio/omap: fix irq loss while in idle with debounce on
Date: Tue, 26 Jun 2012 21:11:08 -0500 [thread overview]
Message-ID: <87y5n9tsg3.fsf@ti.com> (raw)
In-Reply-To: <1339873285-8700-1-git-send-email-notasas@gmail.com> (Grazvydas Ignotas's message of "Sat, 16 Jun 2012 22:01:25 +0300")
Grazvydas Ignotas <notasas@gmail.com> writes:
> It seems that currently GPIO module is not working correctly during idle
> when debounce is enabled - the system almost never responds to button
> presses (observed on OMAP3530 ES2.1 and OMAP3630 ES1.2 pandora boards).
> Even though wakeups are probably working, it seems that the GPIO module
> itself is unable to detect input events and generate interrupts.
> OMAP35x TRM also states that:
> "If the debounce clock is inactive, the debounce cell gates all
> input signals and thus cannot be used."
>
> So whenever we are disabling debounce clocks (for PM or other reasons),
> be sure the module's debounce feature is disabled too.
>
> Cc: Kevin Hilman <khilman@ti.com>
> Signed-off-by: Grazvydas Ignotas <notasas@gmail.com>
This looks right, thanks for the patch.
I will queue it up for v3.6 and get it some broader testing before
sending to Grant.
Kevin
> ---
> drivers/gpio/gpio-omap.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
> index c4ed172..ff213e7 100644
> --- a/drivers/gpio/gpio-omap.c
> +++ b/drivers/gpio/gpio-omap.c
> @@ -174,12 +174,22 @@ static inline void _gpio_dbck_enable(struct gpio_bank *bank)
> if (bank->dbck_enable_mask && !bank->dbck_enabled) {
> clk_enable(bank->dbck);
> bank->dbck_enabled = true;
> +
> + __raw_writel(bank->dbck_enable_mask,
> + bank->base + bank->regs->debounce_en);
> }
> }
>
> static inline void _gpio_dbck_disable(struct gpio_bank *bank)
> {
> if (bank->dbck_enable_mask && bank->dbck_enabled) {
> + /*
> + * Disable debounce before cutting it's clock. If debounce is
> + * enabled but the clock is not, GPIO module seems to be unable
> + * to detect events and generate interrupts at least on OMAP3.
> + */
> + __raw_writel(0, bank->base + bank->regs->debounce_en);
> +
> clk_disable(bank->dbck);
> bank->dbck_enabled = false;
> }
prev parent reply other threads:[~2012-06-27 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 19:01 [PATCH] gpio/omap: fix irq loss while in idle with debounce on Grazvydas Ignotas
2012-06-27 2:11 ` 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=87y5n9tsg3.fsf@ti.com \
--to=khilman@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@stericsson.com \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.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