From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: OMAP: Work around hardcoded interrupts
Date: Mon, 19 Jan 2015 12:12:54 -0800 [thread overview]
Message-ID: <20150119201253.GF18552@atomide.com> (raw)
In-Reply-To: <20150119201404.GA18738@kahuna>
* Nishanth Menon <nm@ti.com> [150119 12:17]:
> On 10:21-20150117, Marc Zyngier wrote:
> > Commit 9a1091ef0017 (irqchip: gic: Support hierarchy irq domain)
> should have been
> Commit 9a1091ef0017 ("irqchip: gic: Support hierarchy irq domain")
>
> > changed the GIC driver to use a non-legacy IRQ domain on DT
> > platforms. This patch assumes that DT-driven systems are getting
> > all of their interrupts from device tree.
> >
> > Turns out that OMAP has quite a few hidden gems, and still uses
> > hardcoded interrupts despite having fairly complete DTs.
> >
> > This patch attempts to work around these by offering a translation
> > method that can be called directly from the hwmod code, if present.
> > The same hack is sprinkled over PRCM and TWL.
> >
> > It isn't pretty, but it seems to do the job without having to add
> > more hacks to the interrupt controller code.
> >
> > Tested on OMAP4 (Panda-ES) and OMAP5 (UEVM5432).
> >
> > Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>
> Other than that, This looks good to me.
> Acked-by: Nishanth Menon <nm@ti.com>
OK thanks applying into omap-for-v3.19/fixes and will send out a
pull request later on today after some make randconfig builds.
Regards,
Tony
next prev parent reply other threads:[~2015-01-19 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 10:21 [PATCH v2] ARM: OMAP: Work around hardcoded interrupts Marc Zyngier
2015-01-17 17:40 ` Tony Lindgren
2015-01-19 20:14 ` Nishanth Menon
2015-01-19 20:12 ` Tony Lindgren [this message]
2015-01-19 21:21 ` Tony Lindgren
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=20150119201253.GF18552@atomide.com \
--to=tony@atomide.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).