From: David Hawkins <dwh@ovro.caltech.edu>
To: Jeff Hane <jeff.hane@maxim-ic.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: PCI interrupt question
Date: Thu, 03 Dec 2009 09:11:38 -0800 [thread overview]
Message-ID: <4B17F14A.1060001@ovro.caltech.edu> (raw)
In-Reply-To: <1259821316.12651.26.camel@qu102.quarc.com>
Hi Jeff,
> I'm trying to get interrupts working for my PCI device on a 460ex and
> am having problem. My ISR never triggers.
>
> I'm new to PCI(and ppc) and LDD said that I could read the config reg
> INTURRUPT_LINE to get the interrupt assigned to my PCI device. Well,
> this always reads zero.
>
> After reading through the code it appears that the interrupt is being
> assigned after reading some information out of the device tree and then
> filling in the irg in the pci_dev structure.
>
> I'm just looking for confirmation that I should be calling request_irq
> with the irq that I found in the pci_dev struct.
Can you clarify:
1. 460EX is your PCI host CPU?
2. You have some PCI device - what? Have you tested it works in a
standard PCI bus? Eg. ran lspci from an x86 host.
3. When your host processor boots, it assigns the PCI resources.
On an x86, its the BIOS that assigns the PCI addresses and IRQs
on the PCI devices. For your 460EX, it could be your bootloader,
or it could be your host OS (Linux).
4. If you boot Linux on your 460EX and run lspci, and the device
configuration space register for the IRQ line is 0, then your
host has not setup the PCI interface on your device correctly.
5. Once you have the PCI IRQ assigned to the device correctly,
you need to know which IRQ line on the host this corresponds to.
I'm pretty sure that needs to be described in the DTS as
commented by Stefan.
These comments might not be 100% correct, but the list of things
to check should be close enough for you to track down your
problem.
Cheers,
Dave
next prev parent reply other threads:[~2009-12-03 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 6:21 PCI interrupt question Jeff Hane
2009-12-03 7:31 ` Stefan Roese
2009-12-03 17:11 ` David Hawkins [this message]
2009-12-03 19:39 ` Jeff Hane
2009-12-03 19:44 ` Ira W. Snyder
2009-12-03 19:52 ` David Hawkins
2009-12-03 19:59 ` Ira W. Snyder
2009-12-03 20:03 ` David Hawkins
2009-12-03 21:28 ` Wolfgang Denk
2009-12-03 21:38 ` David Hawkins
2009-12-04 9:05 ` Benjamin Herrenschmidt
2009-12-04 4:52 ` Stefan Roese
2009-12-04 9:02 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B17F14A.1060001@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=jeff.hane@maxim-ic.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.