Thread (3 messages) 3 messages, 3 authors, 2011-01-04

Re: [RFC] MPIC Bindings and Bindings for AMP Systems

From: Blanchard, Hollis <hidden>
Date: 2011-01-04 20:14:47
Also in: linux-devicetree

Possibly related (same subject, not in this thread)

On 12/23/2010 01:49 PM, Meador Inge wrote:
We can't just remove the IRQ of the _other_ OS from the 'interrupts'=20
property in the message node because we need to know the IRQ in order=20
to talk to the other OS.  So, we use protected sources to tell the OS=20
that an IRQ is not available for its own use, while at the same time=20
keeping=20
complete information on all the IRQ mappings for the message =
registers.
There's a simpler and more fundamental problem: the Linux MPIC driver=20
initializes the "VECPRI" register for all interrupt sources (which is=20
how you associate a source with a vector). We need the Linux driver not=20
to do this.

(The "no-reset" property solves a related problem: it tells the driver=20
not to use the hardware's special "reset all registers" bit.)

Hollis Blanchard
Mentor Graphics, Embedded Systems Division
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help