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 2/6] ARM: tegra: update GPIO chained IRQ handler to use entry/exit functions
Date: Sun, 01 May 2011 13:42:08 +0100	[thread overview]
Message-ID: <1304253728.4547.3.camel@jazzbox> (raw)
In-Reply-To: <BANLkTik4u=f+pFe0mQDV6Moj=-x2JQ1SMQ@mail.gmail.com>

Hi Colin,

On Sun, 2011-05-01 at 08:26 +0100, Colin Cross wrote:
> On Tue, Apr 12, 2011 at 11:35 AM, Will Deacon <will.deacon@arm.com> wrote:
> > This patch updates the Tegra gpio chained IRQ handler to use the chained
> > IRQ enter/exit functions in order to function correctly on primary
> > controllers with different methods of flow control.
> >
> > This is required for the GIC to move to fasteoi interrupt handling.
> >
> > Cc: Colin Cross <ccross@android.com>
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
> > ---
> >  arch/arm/mach-tegra/gpio.c |    9 ++++++---
> >  arch/arm/mach-tegra/irq.c  |   12 ++++++------
> >  2 files changed, 12 insertions(+), 9 deletions(-)

[...]

> This version of the patch contains changes to gpio.c and irq.c.  If
> you drop the irq.c changes (which I will fix in my upcoming patch),

Yes please! I'm more than happy to drop the changes to irq.c. Please CC
me on your patch so that I know when it's safe to continue pushing the
fasteoi change.

> Acked-by: Colin Cross <ccross@android.com>

Cheers,

Will

  reply	other threads:[~2011-05-01 12:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 18:35 [PATCH v2 0/6] Use chained handler entry/exit functions in platform code Will Deacon
2011-04-12 18:35 ` [PATCH 1/6] ARM: omap: update GPIO chained IRQ handler to use entry/exit functions Will Deacon
2011-04-12 18:35 ` [PATCH 2/6] ARM: tegra: " Will Deacon
2011-05-01  7:26   ` Colin Cross
2011-05-01 12:42     ` Will Deacon [this message]
2011-04-12 18:35 ` [PATCH 3/6] ARM: s5pv310: update IRQ combiner to use chained " Will Deacon
2011-04-12 18:35 ` [PATCH 4/6] ARM: msm: update GPIO chained IRQ handler to use " Will Deacon
2011-04-15 18:27   ` David Brown
2011-04-18 17:57     ` Will Deacon
2011-04-16  1:51   ` Abhijeet Dharmapurikar
2011-04-18 17:56     ` Will Deacon
2011-04-12 18:35 ` [PATCH 5/6] ARM: nmk: update GPIO chained IRQ handler to " Will Deacon
2011-04-18 18:26   ` Linus Walleij
2011-04-18 19:04     ` Will Deacon
2011-04-18 23:46       ` Linus Walleij
2011-04-19 19:52         ` Grant Likely
2011-04-12 18:35 ` [PATCH 6/6] ARM: gic: use handle_fasteoi_irq for SPIs Will Deacon
2011-04-16  1:52   ` Abhijeet Dharmapurikar
2011-04-19 11:20   ` Santosh Shilimkar
2011-04-19 15:16     ` Will Deacon
2011-04-20  4:20       ` Santosh Shilimkar
2011-04-30  2:38   ` Colin Cross
2011-04-30  9:54     ` Thomas Gleixner
2011-04-30 16:42       ` Colin Cross
  -- strict thread matches above, loose matches on Subject: below --
2011-04-01 14:50 [PATCH 0/6] Use chained handler entry/exit functions in platform code Will Deacon
2011-04-01 14:50 ` [PATCH 2/6] ARM: tegra: update GPIO chained IRQ handler to use entry/exit functions Will Deacon
2011-04-01 20:29   ` Colin Cross
2011-04-03 12:13     ` 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=1304253728.4547.3.camel@jazzbox \
    --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).