From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Feng Tang <feng.tang@intel.com>, Alek Du <alek.du@intel.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [patch 4/5] gpio: langwell: Simplify demux loop
Date: Thu, 17 Mar 2011 19:32:55 -0000 [thread overview]
Message-ID: <20110317192449.744944033@linutronix.de> (raw)
In-Reply-To: <20110317192247.722047296@linutronix.de>
[-- Attachment #1: gpio-langwell-simplify-loop.patch --]
[-- Type: text/plain, Size: 1467 bytes --]
Use __ffs() to find the pending interrupt source instead of looping 32
times.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Feng Tang <feng.tang@intel.com>
Cc: Alek Du <alek.du@intel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
---
drivers/gpio/langwell_gpio.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
Index: linux-2.6-tip/drivers/gpio/langwell_gpio.c
===================================================================
--- linux-2.6-tip.orig/drivers/gpio/langwell_gpio.c
+++ linux-2.6-tip/drivers/gpio/langwell_gpio.c
@@ -191,19 +191,20 @@ static void lnw_irq_handler(unsigned irq
struct lnw_gpio *lnw = irq_data_get_irq_handler_data(data);
struct irq_chip *chip = irq_data_get_irq_chip(data);
u32 base, gpio, gedr_v;
+ unsigned long pending;
void __iomem *gedr;
/* check GPIO controller to check which pin triggered the interrupt */
for (base = 0; base < lnw->chip.ngpio; base += 32) {
gedr = gpio_reg(&lnw->chip, base, GEDR);
- gedr_v = readl(gedr);
+ gedr_v = pending = readl(gedr);
if (!gedr_v)
continue;
- for (gpio = base; gpio < base + 32; gpio++)
- if (gedr_v & BIT(gpio % 32)) {
- pr_debug("pin %d triggered\n", gpio);
- generic_handle_irq(lnw->irq_base + gpio);
- }
+ while (pending) {
+ gpio = __ffs(pending) - 1;
+ pending &= ~BIT(gpio);
+ generic_handle_irq(lnw->irq_base + base + gpio);
+ }
/* clear the edge detect status bit */
writel(gedr_v, gedr);
}
next prev parent reply other threads:[~2011-03-17 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 19:32 [patch 0/5] gpio: langwell: Cleanup the interrupt mess Thomas Gleixner
2011-03-17 19:32 ` [patch 1/5] gpio; Make Intel chipset gpio drivers depend on x86 Thomas Gleixner
2011-03-17 19:32 ` [patch 2/5] gpio-langwell-fix-crap.patch Thomas Gleixner
2011-03-17 19:32 ` [patch 3/5] gpio: langwell: Convert irq name space Thomas Gleixner
2011-03-17 19:32 ` Thomas Gleixner [this message]
2011-03-17 19:32 ` [patch 5/5] [RFC] gpio: langwell: Clear edge bit before handling Thomas Gleixner
2011-03-18 2:33 ` Du, Alek
2011-03-18 5:06 ` Grant Likely
2011-03-17 19:51 ` [patch 0/5] gpio: langwell: Cleanup the interrupt mess Grant Likely
2011-03-17 21:38 ` Thomas Gleixner
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=20110317192449.744944033@linutronix.de \
--to=tglx@linutronix.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alek.du@intel.com \
--cc=feng.tang@intel.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome