From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Jeff Hane <jeff.hane@maxim-ic.com>
Subject: Re: PCI interrupt question
Date: Thu, 3 Dec 2009 08:31:58 +0100 [thread overview]
Message-ID: <200912030831.58528.sr@denx.de> (raw)
In-Reply-To: <1259821316.12651.26.camel@qu102.quarc.com>
Hi Jeff,
On Thursday 03 December 2009 07:21:56 Jeff Hane wrote:
> I'm trying to get interrupts working for my PCI device on a 460ex and
> am having problem. My ISR never triggers.
Which 460EX board is this? Canyonlands or some custom board?
> 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.
Yes. The device tree has to describe the PCI interrupt layout.
> I'm just looking for confirmation that I should be calling request_irq
> with the irq that I found in the pci_dev struct.
Yes.
Canyonlands dts correctly describes the PCI interrupts assignments. If you
have a custom 460EX board, then you probably have a different interrupt routed
to the PCI slot. This needs to be described in your device tree file.
Cheers,
Stefan
next prev parent reply other threads:[~2009-12-03 7:32 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 [this message]
2009-12-03 17:11 ` David Hawkins
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=200912030831.58528.sr@denx.de \
--to=sr@denx.de \
--cc=jeff.hane@maxim-ic.com \
--cc=linuxppc-dev@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).