linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 00/17] Switch GIC users (and omap2plus) to CONFIG_MULTI_IRQ_HANDLER
Date: Fri,  4 Nov 2011 16:57:34 +0000	[thread overview]
Message-ID: <1320425871-30564-1-git-send-email-marc.zyngier@arm.com> (raw)

In order to support multiple primary interrupt controllers in the same
image, it is necessary to use the MULTI_IRQ_HANDLER config option.

This patch series makes a first step in that direction by:
- having the GIC code to provides a global handler,
- make GIC users to provide this handler from their machine descriptor.

A side effect of this is that it forces OMAP2/3 platforms to be
converted too in order to preserve the MULTI_OMAP feature. This leads
to a certain simplification of the interrupt handling for the
OMAP2/3/4 platforms.

This series has been tested by myself on VE (A9, A5, A15), PB11MP,
Panda, IGEPv2, Harmony and Origen, as well as on other platforms by
people who tested it. Patches against next-20111104 plus my "ARM: gic:
allow GIC to support non-banked setups" patch.

             reply	other threads:[~2011-11-04 16:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 16:57 Marc Zyngier [this message]
2011-11-04 16:57 ` [PATCH v3 01/17] ARM: Make global handler and CONFIG_MULTI_IRQ_HANDLER mutually exclusive Marc Zyngier
2011-11-04 18:30   ` Nicolas Pitre
2011-11-04 20:37   ` Eric Miao
2011-11-07  9:45   ` Jamie Iles
2011-11-07 11:02     ` Linus Walleij
2011-11-07 11:12       ` Marc Zyngier
2011-11-07 11:17         ` Jamie Iles
2011-11-07 11:22           ` Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 02/17] ARM: mxc: rename gic_handle_irq to avoid name clash Marc Zyngier
2011-11-04 21:09   ` Shawn Guo
2011-11-04 16:57 ` [PATCH v3 03/17] ARM: GIC: Add global gic_handle_irq() function Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 04/17] ARM: mxc: convert smp platforms to global gic_handle_irq() Marc Zyngier
2011-11-04 21:15   ` Shawn Guo
2011-11-07 14:01     ` Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 05/17] ARM: highbank: convert to CONFIG_MULTI_IRQ_HANDLER Marc Zyngier
2011-11-04 18:30   ` Rob Herring
2011-11-04 16:57 ` [PATCH v3 06/17] ARM: RealView: " Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 07/17] ARM: VExpress: " Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 08/17] ARM: msm: convert SMP platforms " Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 09/17] ARM: exynos4: convert " Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 10/17] ARM: tegra2: " Marc Zyngier
2011-11-04 19:48   ` Olof Johansson
2011-11-04 16:57 ` [PATCH v3 11/17] ARM: ux500: " Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 12/17] ARM: shmobile: convert smp platforms to gic_handle_irq() Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 13/17] ARM: cns3xxx: convert to CONFIG_MULTI_IRQ_HANDLER Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 14/17] ARM: zynq: " Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 15/17] ARM: omap2/3: Add global omap2/3_intc_handle_irq() functions Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 16/17] ARM: omap2plus: convert to CONFIG_MULTI_IRQ_HANDLER Marc Zyngier
2011-11-04 16:57 ` [PATCH v3 17/17] ARM: GIC: Make MULTI_IRQ_HANDLER mandatory Marc Zyngier

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=1320425871-30564-1-git-send-email-marc.zyngier@arm.com \
    --to=marc.zyngier@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).