* Determining pci bus from irq
@ 2003-09-09 16:10 Adam Litke
2003-09-09 17:09 ` Alan Cox
0 siblings, 1 reply; 4+ messages in thread
From: Adam Litke @ 2003-09-09 16:10 UTC (permalink / raw)
To: linux-kernel
Is there a nice way to determine, given an irq number, the pci bus
number that raised the interrupt?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Determining pci bus from irq
2003-09-09 16:10 Determining pci bus from irq Adam Litke
@ 2003-09-09 17:09 ` Alan Cox
2003-09-09 17:36 ` Richard B. Johnson
0 siblings, 1 reply; 4+ messages in thread
From: Alan Cox @ 2003-09-09 17:09 UTC (permalink / raw)
To: Adam Litke; +Cc: Linux Kernel Mailing List
On Maw, 2003-09-09 at 17:10, Adam Litke wrote:
> Is there a nice way to determine, given an irq number, the pci bus
> number that raised the interrupt?
In general the answer is you can't find out. PCI IRQ lines are shared.
You can certainly lock and walk the pci device list looking for matches
but you may get a lot of devices on different busses
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Determining pci bus from irq
2003-09-09 17:09 ` Alan Cox
@ 2003-09-09 17:36 ` Richard B. Johnson
2003-09-09 21:20 ` Alan Cox
0 siblings, 1 reply; 4+ messages in thread
From: Richard B. Johnson @ 2003-09-09 17:36 UTC (permalink / raw)
To: Alan Cox; +Cc: Adam Litke, Linux Kernel Mailing List
On Tue, 9 Sep 2003, Alan Cox wrote:
> On Maw, 2003-09-09 at 17:10, Adam Litke wrote:
> > Is there a nice way to determine, given an irq number, the pci bus
> > number that raised the interrupt?
>
> In general the answer is you can't find out. PCI IRQ lines are shared.
> You can certainly lock and walk the pci device list looking for matches
> but you may get a lot of devices on different busses
>
Unless you've got a 'scope. If a device is interrupting often
or if it can be made to interrupt. you can look at the pin on
the PCI card. For some reason, on ix86, the logical "pin" is
always "A", regardless of the device, so you only have one
interrupt line connected to each slot. On lap-tops, there is
often only one IRQ shared for everything IRQ9 for Compaq.
These interrupt lines are usually not physically connected
together. They are ORed in some glue chip so you can see
what card is actually operating the line. On PCI, the IRQ
pin is (+) for TRUE, normally pulled down, and never floating.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Determining pci bus from irq
2003-09-09 17:36 ` Richard B. Johnson
@ 2003-09-09 21:20 ` Alan Cox
0 siblings, 0 replies; 4+ messages in thread
From: Alan Cox @ 2003-09-09 21:20 UTC (permalink / raw)
To: root; +Cc: Adam Litke, Linux Kernel Mailing List
On Maw, 2003-09-09 at 18:36, Richard B. Johnson wrote:
> Unless you've got a 'scope. If a device is interrupting often
> or if it can be made to interrupt. you can look at the pin on
> the PCI card. For some reason, on ix86, the logical "pin" is
> always "A", regardless of the device, so you only have one
> interrupt line connected to each slot. On lap-tops, there is
> often only one IRQ shared for everything IRQ9 for Compaq.
Multifunction devices may well use more than INTA. A PC does
normally use INTA for each device and barberpole the ABCD lines
between slots
Quad ethernet cards using ABCD seem common
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-09-09 21:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-09 16:10 Determining pci bus from irq Adam Litke
2003-09-09 17:09 ` Alan Cox
2003-09-09 17:36 ` Richard B. Johnson
2003-09-09 21:20 ` Alan Cox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®