From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] ARM: gic: consolidate PPI handling
Date: Tue, 27 Sep 2011 17:59:04 -0700 [thread overview]
Message-ID: <20110928005904.GR6324@atomide.com> (raw)
In-Reply-To: <1316793788-14500-3-git-send-email-marc.zyngier@arm.com>
* Marc Zyngier <marc.zyngier@arm.com> [110923 12:03]:
> PPI handling is a bit of an odd beast. It uses its own low level
> handling code and is hardwired to the local timers (hence lacking
> a registration interface).
>
> Instead, switch the low handling to the normal SPI handling code.
> PPIs are handled by the handle_percpu_devid_irq flow.
>
> This also allows the removal of some duplicated code.
>
> Cc: Kukjin Kim <kgene.kim@samsung.com>
> Cc: David Brown <davidb@codeaurora.org>
> Cc: Bryan Huntsman <bryanh@codeaurora.org>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Paul Mundt <lethal@linux-sh.org>
> Cc: Magnus Damm <magnus.damm@gmail.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
For the omap changes:
Tested-by: Tony Lindgren <tony@atomide.com>
(Sorry had to dig this one from the archive, looks like
the Cc addresses might be left out)
next prev parent reply other threads:[~2011-09-28 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 16:03 [PATCH v3 0/3] genirq: handling GIC per-cpu interrupts Marc Zyngier
2011-09-23 16:03 ` [PATCH v3 1/3] genirq: add support for per-cpu dev_id interrupts Marc Zyngier
2011-09-29 5:56 ` Abhijeet Dharmapurikar
2011-09-30 11:08 ` Marc Zyngier
2011-09-23 16:03 ` [PATCH v3 2/3] ARM: gic: consolidate PPI handling Marc Zyngier
2011-09-28 0:59 ` Tony Lindgren [this message]
2011-09-23 16:03 ` [PATCH v3 3/3] ARM: gic, local timers: use the request_percpu_irq() interface Marc Zyngier
2011-09-26 20:18 ` [PATCH v3 0/3] genirq: handling GIC per-cpu interrupts David Brown
2011-09-27 0:11 ` David Brown
2011-09-27 10:21 ` Shawn Guo
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=20110928005904.GR6324@atomide.com \
--to=tony@atomide.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).