From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] nmk-gpio: use request_irq instead of chained handler
Date: Fri, 25 Feb 2011 17:16:25 -0000 [thread overview]
Message-ID: <000c01cbd50f$bbc24d50$3346e7f0$@deacon@arm.com> (raw)
In-Reply-To: <AANLkTin_xxPJnOKxiu-z=Yo2FVkD=_Ow7CoGb2gApUaq@mail.gmail.com>
Hi Linus,
> 2011/2/23 Will Deacon <will.deacon@arm.com>:
> >> On Wed, Feb 23, 2011 at 22:47, Will Deacon <will.deacon@arm.com> wrote:
> >> >> __nmk_gpio_irq_handler doesn't do anything more that what a normal handler
> >> >> does, so it can become one. ?This is also needed for changing the GIC
> >> >> implementation to a different flow handler.
> >> >>
> >> >> Signed-off-by: Rabin Vincent <rabin.vincent@stericsson.com>
> >> >
> >> > mach-nomadik only seems to use the vic. Why does this GPIO handler
> >> > need updating?
> >>
> >> plat-nomadik/gpio.c is also used by mach-ux500, which uses the GIC.
> >
> > Ah yes, sorry I missed that one. I'm happy to include any patches from you
> > in the GIC fasteoi series if it makes merging easier.
>
> OK if this one is OK I sure prefer that you take it in your series Will,
> since you have the whole picture of what you want to do with the
> GIC.
>
> It'll likely collide with the stuff I have stacked up for the 2.6.39 merge
> window though, which will be pull-requested any day now.
Sure. I'll add a patch to my series that makes the minimal change required
and post it next week.
Will
prev parent reply other threads:[~2011-02-25 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 12:54 [PATCH] nmk-gpio: use request_irq instead of chained handler Rabin Vincent
2011-02-23 13:18 ` Russell King - ARM Linux
2011-02-23 15:22 ` Rabin Vincent
2011-02-23 17:17 ` Will Deacon
[not found] ` <-6148324460357957969@unknownmsgid>
2011-02-23 17:25 ` Rabin Vincent
2011-02-23 17:36 ` Will Deacon
[not found] ` <5890487119819559395@unknownmsgid>
2011-02-25 16:59 ` Linus Walleij
2011-02-25 17:16 ` Will Deacon [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='000c01cbd50f$bbc24d50$3346e7f0$@deacon@arm.com' \
--to=will.deacon@arm.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).