Thread (1 message) 1 message, 1 author, 2010-09-22

Regarding hw irq to Linux irq mapping on ARM

From: Grant Likely <hidden>
Date: 2010-09-22 11:52:18
Also in: linux-devicetree


"Shaju Abraham" [off-list ref] wrote:
On Wed, Sep 22, 2010 at 3:32 AM, Benjamin Herrenschmidt
[off-list ref] wrote:
quoted
The main grief one could have with my scheme is the naming of irq_host
which has confused people in the past. It should probably be irq_domain
to make clear what it is. It generally have a 1:1 relationship to the
irq_chip but there are cases where that isn't the case (essentially
where you have multiple irq_chip per domain) for various reasons so it's
better to keep those separate.
How do we handle multiplexed interrupts ? For example a single interrupt line
representing multple irq sources.
We have ARM systems with  single interrupt line on a VIC  muxed to
192 different GPIO sources (each capable of generating interrupts). For such a
system the virq to hw irq mapping can get complex.
Assign a separate irq number to each gpio.  In effect, this makes the gpio controller an irq controller.

g.

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help