linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] irqchip: intc-irqpin: Add support for shared interrupt lines
Date: Wed, 27 Mar 2013 23:04:56 +0900	[thread overview]
Message-ID: <20130327140456.GC4324@verge.net.au> (raw)
In-Reply-To: <CABYn4sx_pRxgdM3kD3okmt8xbCFas+T0cczQO=RF75Q8Bt2e_Q@mail.gmail.com>

On Wed, Mar 27, 2013 at 02:50:05PM +0100, Bastian Hecht wrote:
> Hi Simon,
> 
> 2013/3/27 Simon Horman <horms@verge.net.au>:
> > On Tue, Mar 26, 2013 at 12:18:18PM +0100, Bastian Hecht wrote:
> >> On some hardware we don't have a 1-1 mapping from the external
> >> interrupts coming from INTC to the GIC SPI pins. We can however
> >> share lines to demux incoming IRQs on these SoCs.
> >>
> >> This patch enables the intc_irqpin driver to detect requests for shared
> >> interrupt lines and demuxes them properly by querying the INTC INTREQx0A
> >> registers.
> >>
> >> If you need multiple shared intc_irqpin device instances, be sure to mask
> >> out all interrupts on the INTC that share the one line before you start
> >> to register them. Else you run into IRQ floods that would be caused by
> >> interrupts for which no handler has been set up yet when the first
> >> intc_irqpin device is registered.
> >>
> >> Signed-off-by: Bastian Hecht <hechtb+renesas@gmail.com>
> >> Acked-by: Magnus Damm <damm@opensource.se>
> >
> > Thanks, I will see about queuing up these changes for v3.10.
> >
> >
> > I believe that with these changes it should be possible to rebase/rework
> > armadillo800eva-reference so that it no longer uses the unmerged INTC
> > DT bindings. Would it be possible for you to see about making a fresh
> > version of armadillo800eva-reference that is based on the next branch
> > in the Renesas tree plus this series of two patches?
> 
> yes ok, I'll prepare a new armadillo reference version. The patches
> were based on all+next, but I'll post a v4 rebased on next.

Thanks, sorry for the bother.

I have just pushed a fresh next branch and taged it as
renesas-next-20130327. If you quote that as your base I should
be able to apply your series without a hitch.

> I'll post a separate patch series for the reference code if you don't
> mind, as this might take a few days to be done.

Sure, no problem.

  reply	other threads:[~2013-03-27 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 11:18 [PATCH v3 1/2] irqchip: intc-irqpin: Add support for shared interrupt lines Bastian Hecht
2013-03-26 11:18 ` [PATCH v3 2/2] ARM: shmobile: r8a7740: Migrate from INTC to GIC Bastian Hecht
2013-03-27  5:04   ` Simon Horman
2013-03-27  6:12   ` Kuninori Morimoto
2013-03-27  4:59 ` [PATCH v3 1/2] irqchip: intc-irqpin: Add support for shared interrupt lines Simon Horman
2013-03-27 13:50   ` Bastian Hecht
2013-03-27 14:04     ` Simon Horman [this message]
2013-03-27 14:11       ` Simon Horman
2013-04-03  7:46     ` Simon Horman
2013-04-04 13:47       ` Bastian Hecht
2013-04-05  0:36         ` Simon Horman
2013-04-08 11:03           ` Bastian Hecht

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=20130327140456.GC4324@verge.net.au \
    --to=horms@verge.net.au \
    --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).