mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH 4/4] MIPS: JZ4740: GPIO: Check correct IRQ in demux handler
Date: Fri,  3 Jun 2011 03:06:51 +0200	[thread overview]
Message-ID: <1307063211-10098-4-git-send-email-lars@metafoo.de> (raw)
In-Reply-To: <1307063211-10098-1-git-send-email-lars@metafoo.de>

Check the trigger direction for the triggered IRQ instead of the parent IRQ.

Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
---
 arch/mips/jz4740/gpio.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/mips/jz4740/gpio.c b/arch/mips/jz4740/gpio.c
index f3590a2..7179c78 100644
--- a/arch/mips/jz4740/gpio.c
+++ b/arch/mips/jz4740/gpio.c
@@ -309,7 +309,7 @@ static void jz_gpio_irq_demux_handler(unsigned int irq, struct irq_desc *desc)
 
 	gpio_irq = chip->irq_base + __fls(flag);
 
-	jz_gpio_check_trigger_both(chip, irq);
+	jz_gpio_check_trigger_both(chip, gpio_irq);
 
 	generic_handle_irq(gpio_irq);
 };
-- 
1.7.2.5


  parent reply	other threads:[~2011-06-03  1:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03  1:06 [PATCH 1/4] PM / MIPS: Use struct syscore_ops instead of sysdevs for PM (v2) Lars-Peter Clausen
2011-06-03  1:06 ` [PATCH 2/4] MIPS: JZ4740: Use generic irq chip Lars-Peter Clausen
2011-08-18 18:11   ` Ralf Baechle
2011-06-03  1:06 ` [PATCH 3/4] MIPS: JZ4740: GPIO: Simplify IRQ demuxer Lars-Peter Clausen
2011-08-18 18:11   ` Ralf Baechle
2011-06-03  1:06 ` Lars-Peter Clausen [this message]
2011-08-18 18:11   ` [PATCH 4/4] MIPS: JZ4740: GPIO: Check correct IRQ in demux handler Ralf Baechle
2011-08-18 17:56 ` [PATCH 1/4] PM / MIPS: Use struct syscore_ops instead of sysdevs for PM (v2) Ralf Baechle

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=1307063211-10098-4-git-send-email-lars@metafoo.de \
    --to=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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

all inboxes | Powered by JetHome®