Thread (4 messages) flat view 4 messages, 4 authors, 2009-03-04

Re: mpc8349e-mitx 2.6.25 serial IRQ assigned wrong

From: Grant Likely <hidden>
Date: 2009-03-04 23:08:02

On Tue, Mar 3, 2009 at 10:39 PM, Steve DeLaney [off-list ref] wrote:
I didn't realize before that /proc/interrupts
serviced by irq.c show_interrupts() displays virtual vector numbers.

For the mpc8349e-mitx this must be incorrect since there is no ISA?
Essentially all that is needed is a 1:1 mapping hirq:virq since
each interrupt source in the system appears to have a unique vector
in the SOC IPIC. =A0It seems this scheme is needlessly complex, at least =
for
mpc8349e.
It may look to be needlessly complex for boards that only have one
interrupt controller, but it is far simpler than the alternative when
you have boards with multiple cascaded IRQ controllers.  This is not
an uncommon circumstance any more, even on embedded boards.  ie. I'm
working on two different MPC5200 platforms and each has an FPGA which
coalesces interrupts to a single MPC5200 external IRQ line.

Without VIRQs, I'd need to slice up the IRQ number space for each
board variant I work with and write the code to match.  With VIRQs,
there is no need to, and all of the boards can use common support
code.

g.
.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help