From: tarun.kanti@ti.com (Tarun Kanti DebBarma)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 REPOST 20/25] gpio/omap: fix incorrect access of debounce module
Date: Tue, 27 Dec 2011 21:39:31 +0530 [thread overview]
Message-ID: <1325002176-25626-21-git-send-email-tarun.kanti@ti.com> (raw)
In-Reply-To: <1325002176-25626-1-git-send-email-tarun.kanti@ti.com>
Enable debounce clock before writing/reading debounce registers.
Disable the clock at the end so that it is synchronized with the
pm_runtime_get/put_sync calls.
Enable debounce clock per module. This call is mandatory because
in omap_gpio_request() when *_runtime_get_sync() is called,
_gpio_dbck_enable() within runtime callbck fails to turn on dbck
because dbck_enable_mask used within _gpio_dbck_enable() is still
not initialized at that point. Therefore we have to enable dbck here.
Signed-off-by: Tarun Kanti DebBarma <tarun.kanti@ti.com>
Reviewed-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
---
drivers/gpio/gpio-omap.c | 18 +++++++++++++-----
1 files changed, 13 insertions(+), 5 deletions(-)
diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
index 0ea3dc9..7515382 100644
--- a/drivers/gpio/gpio-omap.c
+++ b/drivers/gpio/gpio-omap.c
@@ -203,22 +203,30 @@ static void _set_gpio_debounce(struct gpio_bank *bank, unsigned gpio,
l = GPIO_BIT(bank, gpio);
+ clk_enable(bank->dbck);
reg = bank->base + bank->regs->debounce;
__raw_writel(debounce, reg);
reg = bank->base + bank->regs->debounce_en;
val = __raw_readl(reg);
- if (debounce) {
+ if (debounce)
val |= l;
- clk_enable(bank->dbck);
- } else {
+ else
val &= ~l;
- clk_disable(bank->dbck);
- }
bank->dbck_enable_mask = val;
__raw_writel(val, reg);
+ clk_disable(bank->dbck);
+ /*
+ * Enable debounce clock per module.
+ * This call is mandatory because in omap_gpio_request() when
+ * *_runtime_get_sync() is called, _gpio_dbck_enable() within
+ * runtime callbck fails to turn on dbck because dbck_enable_mask
+ * used within _gpio_dbck_enable() is still not initialized at
+ * that point. Therefore we have to enable dbck here.
+ */
+ _gpio_dbck_enable(bank);
}
static inline void set_gpio_trigger(struct gpio_bank *bank, int gpio,
--
1.7.0.4
next prev parent reply other threads:[~2011-12-27 16:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 16:09 [PATCH v9 REPOST 00/25] gpio/omap: driver cleanup and fixes Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 01/25] gpio/omap: remove dependency on gpio_bank_count Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 02/25] gpio/omap: use flag to identify wakeup domain Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 03/25] gpio/omap: make gpio_context part of gpio_bank structure Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 04/25] gpio/omap: handle save/restore context in GPIO driver Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 05/25] gpio/omap: make non-wakeup GPIO part of pdata Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 06/25] gpio/omap: avoid cpu checks during module ena/disable Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 07/25] gpio/omap: further cleanup using wkup_en register Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 08/25] gpio/omap: use level/edge detect reg offsets Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 09/25] gpio/omap: remove hardcoded offsets in context save/restore Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 10/25] gpio/omap: cleanup set_gpio_triggering function Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 11/25] gpio/omap: cleanup omap_gpio_mod_init function Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 12/25] gpio/omap: use pinctrl offset instead of macro Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 13/25] gpio/omap: remove unnecessary bit-masking for read access Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 14/25] gpio/omap: remove bank->method & METHOD_* macros Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 15/25] gpio/omap: fix bankwidth for OMAP7xx MPUIO Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 16/25] gpio/omap: use pm-runtime framework Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 17/25] gpio/omap: optimize suspend and resume functions Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 18/25] gpio/omap: cleanup prepare_for_idle and resume_after_idle Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 19/25] gpio/omap: fix debounce clock handling Tarun Kanti DebBarma
2011-12-27 16:09 ` Tarun Kanti DebBarma [this message]
2011-12-27 16:09 ` [PATCH v9 REPOST 21/25] gpio/omap: remove omap_gpio_save_context overhead Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 22/25] gpio/omap: save and restore debounce registers Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 23/25] gpio/omap: enable irq at the end of all configuration in restore Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 24/25] gpio/omap: restore OE only after setting the output level Tarun Kanti DebBarma
2011-12-27 16:09 ` [PATCH v9 REPOST 25/25] gpio/omap: handle set_dataout reg capable IP on restore Tarun Kanti DebBarma
2012-01-10 0:57 ` [PATCH v9 REPOST 00/25] gpio/omap: driver cleanup and fixes Kevin Hilman
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=1325002176-25626-21-git-send-email-tarun.kanti@ti.com \
--to=tarun.kanti@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).