linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/7] Migrate GIC to fasteoi flow control
Date: Tue,  8 Mar 2011 17:13:18 +0000	[thread overview]
Message-ID: <1299604405-12960-1-git-send-email-will.deacon@arm.com> (raw)

Hello,

This is version 3 of the patch series originally posted here:

v1.) http://lists.infradead.org/pipermail/linux-arm-kernel/2011-February/043083.html
v2.) http://lists.infradead.org/pipermail/linux-arm-kernel/2011-February/043984.html

Changes since v2:

	* Added chained_irq_{enter,exit} functions to work with chained
	  handlers that support multiple primary chips and to aid in
	  bisectibility
	* Based on 2.6.38-rc8

As a result of these changes, all of the BSP code has been reworked so
I'm afraid I need some fresh acks and tested-bys because the old ones
are no longer valid.

I appreciate there is some debate concerning the sanity of chained
handlers with potentially multiple primary chips, but I can't think of
a way to fix these without considering the handlers on a case-by-case
basis which is not the intent of this patch series.

Cheers,

Will


Will Deacon (7):
  ARM: irq: introduce entry and exit functions for chained handlers
  ARM: omap: update GPIO chained IRQ handler to use entry/exit
    functions
  ARM: tegra: update GPIO chained IRQ handler to use entry/exit
    functions
  ARM: s5pv310: update IRQ combiner to use chained entry/exit functions
  ARM: msm: update GPIO chained IRQ handler to use entry/exit functions
  ARM: nmk: update GPIO chained IRQ handler to entry/exit functions
  ARM: gic: use handle_fasteoi_irq for SPIs

 arch/arm/common/gic.c                |   22 +++++++++-------------
 arch/arm/include/asm/mach/irq.h      |   27 +++++++++++++++++++++++++++
 arch/arm/mach-msm/gpio-v2.c          |    6 +++++-
 arch/arm/mach-s5pv310/irq-combiner.c |    6 ++----
 arch/arm/mach-tegra/gpio.c           |    7 ++++---
 arch/arm/plat-nomadik/gpio.c         |   10 ++--------
 arch/arm/plat-omap/gpio.c            |    7 ++++---
 7 files changed, 53 insertions(+), 32 deletions(-)

             reply	other threads:[~2011-03-08 17:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 17:13 Will Deacon [this message]
2011-03-08 17:13 ` [PATCH 1/7] ARM: irq: introduce entry and exit functions for chained handlers Will Deacon
2011-03-11 16:33   ` Thomas Gleixner
2011-03-11 16:56     ` Will Deacon
2011-03-11 19:19       ` Thomas Gleixner
2011-03-14 13:04         ` Will Deacon
2011-03-08 17:13 ` [PATCH 2/7] ARM: omap: update GPIO chained IRQ handler to use entry/exit functions Will Deacon
2011-03-08 17:13 ` [PATCH 3/7] ARM: tegra: " Will Deacon
2011-03-08 17:13 ` [PATCH 4/7] ARM: s5pv310: update IRQ combiner to use chained " Will Deacon
2011-03-08 17:13 ` [PATCH 5/7] ARM: msm: update GPIO chained IRQ handler to use " Will Deacon
2011-03-08 17:13 ` [PATCH 6/7] ARM: nmk: update GPIO chained IRQ handler to " Will Deacon
2011-03-08 17:13 ` [PATCH 7/7] ARM: gic: use handle_fasteoi_irq for SPIs Will Deacon
2011-03-11 15:59 ` [PATCH v3 0/7] Migrate GIC to fasteoi flow control Will Deacon

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=1299604405-12960-1-git-send-email-will.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).