[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110810141048.GK10121@e102144-lin.cambridge.arm.com>
Date: Wed, 10 Aug 2011 15:10:49 +0100
From: Will Deacon <will.deacon@....com>
To: Rob Herring <robherring2@...il.com>
Cc: Mark Rutland <Mark.Rutland@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"weizeng.he@....com" <weizeng.he@....com>,
"workgroup.linux@....com" <workgroup.linux@....com>,
"'Arnd Bergmann'" <arnd@...db.de>,
"'Barry Song'" <21cnbao@...il.com>,
"'Grant Likely'" <grant.likely@...retlab.ca>,
"'Olof Johansson'" <olof@...om.net>
Subject: Re: Subject: L2x0 OF properties do not include interrupt #
Hi Rob,
On Wed, Aug 10, 2011 at 02:59:12PM +0100, Rob Herring wrote:
> I think you should allow for either the single irq or individual irqs.
> You can specify that the event counter interrupt must be first, then the
> pmu driver could work either way ignoring the rest. The driver probably
> needs to mark the handler as shared if there is only the combined
> interrupt unless you expect all interrupts to be handled by 1 driver.
I much prefer having seperate, individual IRQs with no requirement on
ordering.
Now, the L2 binding also doesn't fit too well for the L2CC on Cortex-A15,
which is an inner cache like the one on Cortex-A8. Because of this, it
doesn't have a base address but it *does* have an IRQ which is how external
aborts are raised.
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists