From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] irqchip: sirf: move from legacy mode to linear irqdomain
Date: Thu, 29 Aug 2013 09:48:50 -0700 [thread overview]
Message-ID: <20130829164850.GB18542@quad.lixom.net> (raw)
In-Reply-To: <CAGsJ_4yfme9pF7AD=uaz-KsXirwK+isfc_yVrWX82LzV8Jf+6w@mail.gmail.com>
On Mon, Aug 19, 2013 at 05:30:31PM +0800, Barry Song wrote:
> 2013/8/6 Barry Song <21cnbao@gmail.com>:
> > the series of patches for irqdomain core in 3.11 has broken sirf
> > irq which uses legacy mapping. all users fail in the new kernel
> > while setupping irq.
> >
> > this patch moves to linear irqdomain and drop old legacy irqdomain
> > codes since we don't need it any more, and at the same time, it
> > also fixes the broken interrupts of sirfsoc in 3.11.
> >
> > on the other hand, we actually only have 64 interrupt sources for
> > prima2 and atlas6, but there are 128 interrupt souces for marco
> > which uses GIC. in the legacy codes, sirf gpio also uses legacy
> > irqdomain, so to make gpio interrupt mapping not depend on the
> > prima2/atlas6/marco an use unified marco,we enlarge prima2/atlas6
> > interrupt number to 128. here we don't need this workaround any
> > more as sirf gpio also moved to linear mode before. so we move
> > SIRFSOC_NUM_IRQS back to 64 too.
> >
> > Signed-off-by: Barry Song <Baohua.Song@csr.com>
>
> ping, this should touch 3.11 as sirfsoc interrupts break in 3.11.
Yeah, apologies for missing this -- applied now and will send up shortly.
-Olof
next prev parent reply other threads:[~2013-08-29 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 5:37 [PATCH 1/2] irqchip: sirf: move from legacy mode to linear irqdomain Barry Song
2013-08-06 5:37 ` [PATCH 2/2] arm: prima2: drop nr_irqs in mach as we moved " Barry Song
2013-08-19 9:30 ` [PATCH 1/2] irqchip: sirf: move from legacy mode " Barry Song
2013-08-29 16:48 ` Olof Johansson [this message]
2013-08-29 16:48 ` Olof Johansson
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=20130829164850.GB18542@quad.lixom.net \
--to=olof@lixom.net \
--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