From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: omap: update GPIO chained IRQ handler to use EOI in parent chip
Date: Tue, 22 Feb 2011 18:30:01 -0000 [thread overview]
Message-ID: <001b01cbd2be$84ea7c10$8ebf7430$@deacon@arm.com> (raw)
In-Reply-To: <bb6bff8b082a50e6b739b22bad6ab6ec@mail.gmail.com>
Hi Santosh,
> > > On OMAP4, gpio_irq_handler can be chained to a physical interrupt
> > > using
> > > the GIC as the primary IRQ chip. Now that the GIC uses the fasteoi
> > > flow
> > > model, the chained handler must invoke ->irq_eoi once handling is
> > > complete.
> > >
> > > This patch adds a conditional call to ->irq_eoi in the GPIO IRQ
> > > handler
> > > for OMAP platforms. For OMAP implementations using other primary
> > > interrupt controllers, the ->irq_ack call remains and is also made
> > > conditional on the support offered by the controller.
> > >
> > > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> > > Cc: Colin Cross <ccross@google.com>
> > > Signed-off-by: Will Deacon <will.deacon@arm.com>
> > > ---
> > Thanks Will for changes. They look fine.
> > Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> >
> > I will test your series tomorrow on OMAP with some
> > GPIO interrupts.
> >
> Tested your series on OMAP4 SDP, where GPIO is used for
> ethernet interrupts. They seems to work as expected.
> For omap changes,
> Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
That's good news, thanks! One down, three to go...
Will
next prev parent reply other threads:[~2011-02-22 18:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 15:28 [PATCH 0/5] Migrate GIC to fasteoi flow control Will Deacon
2011-02-21 15:28 ` [PATCH 1/5] ARM: gic: use handle_fasteoi_irq for SPIs Will Deacon
2011-02-21 15:28 ` [PATCH 2/5] ARM: omap: update GPIO chained IRQ handler to use EOI in parent chip Will Deacon
2011-02-21 19:15 ` Santosh Shilimkar
2011-02-22 14:14 ` Santosh Shilimkar
2011-02-22 18:30 ` Will Deacon [this message]
2011-02-22 18:18 ` Tony Lindgren
2011-02-22 18:32 ` Will Deacon
2011-02-21 15:28 ` [PATCH 3/5] ARM: tegra: " Will Deacon
2011-02-22 19:09 ` Colin Cross
2011-02-22 19:21 ` Will Deacon
2011-02-22 19:52 ` Russell King - ARM Linux
2011-02-23 10:39 ` Will Deacon
2011-02-21 15:28 ` [PATCH 4/5] ARM: s5pv310: update IRQ combiner " Will Deacon
2011-02-23 6:59 ` Kyungmin Park
2011-02-23 15:58 ` Will Deacon
2011-02-21 15:28 ` [PATCH 5/5] ARM: msm: update GPIO chained IRQ handler " Will Deacon
2011-02-24 0:22 ` Abhijeet Dharmapurikar
2011-02-24 12:40 ` Thomas Gleixner
2011-02-24 14:12 ` Will Deacon
2011-02-24 15:42 ` 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='001b01cbd2be$84ea7c10$8ebf7430$@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).