PCI interrupt assignment on sequoia board

[Josh Boyer]

On Wed, 9 Jan 2008 16:53:22 +0100
Matthias Fuchs <matthias.fuchs at esd-electronics.com> wrote:

> Hi,
> 
> I noticed that Josh's 'for-2.5.25' does not assign PCI interrupts correctly:
> 
> bash-3.00# lspci -v
> 00:00.0 Class 0680: 1014:027f
>         Subsystem: 10e8:cafe
>         Flags: bus master, medium devsel, latency 0, IRQ 16
>         Memory at <unassigned> (32-bit, prefetchable)
>         Capabilities: [58] Power Management version 2
> 
> 00:0a.0 Class 0b20: 1014:027f	(this is a PPC440EPx PCI target board in a sequoia PCI slot)
>         Subsystem: 12fe:0441
>         Flags: bus master, medium devsel, latency 128, IRQ 16
>         Memory at 0000000180000000 (32-bit, prefetchable) [size=64M]
>         Memory at 0000000184000000 (32-bit, prefetchable) [size=16M]
>         Capabilities: [58] Power Management version 2
> 
> 00:0c.0 Class 0200: 168c:0013 (rev 01)
>         Subsystem: 14b7:0a60
>         Flags: bus master, medium devsel, latency 128, IRQ 16
>         Memory at 0000000185000000 (32-bit, non-prefetchable) [size=64K]
>         Capabilities: [44] Power Management version 2
> 
> bash-3.00# uname -a
> Linux sequoia 2.6.24-rc6-g78994e24 #5 Wed Jan 9 16:22:31 CET 2008 ppc ppc ppc GNU/Linux
> 
> 
> All interrupts are '16'. But I expected 67 as correctly stated in the device tree.
> This test has been made with the uboot wrapper code.
> 
> Any idea?

Does lspci display the virtual IRQ number that is assigned when the
device tree is parsed and interrupts are mapped?  I think so.  If you
look at the other devices in /proc/interrupts you'll see they have the
virtual IRQ numbers as well.

josh