From: David Hawkins <dwh@ovro.caltech.edu>
To: "Ira W. Snyder" <iws@ovro.caltech.edu>
Cc: Jeff Hane <jeff.hane@maxim-ic.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: PCI interrupt question
Date: Thu, 03 Dec 2009 12:03:55 -0800 [thread overview]
Message-ID: <4B1819AB.1030002@ovro.caltech.edu> (raw)
In-Reply-To: <20091203195908.GA17100@ovro.caltech.edu>
Hi Ira,
> When Linux is assigning BARs and IRQs, it writes the BAR addresses to
> the PCI cards, but does not write the IRQ. This was my experience with
> PCI hotplug.
Ooh, subtle.
>> Bottom line is; if the IRQ field of lspci is 0, then you
>> need to figure out that problem first :)
>>
>
> In the PCI hotplug case mentioned above, lspci would show the IRQ as 0
> until I called request_irq() in the kernel. Afterwards, the correct IRQ
> showed up in the lspci output.
>
> Try request_irq(pdev->irq, ....) and see if it works.
You can also try lscpi -xxx, and setpci for writing the
registers. So try cheating and writing to the IRQ register
in the PCI interface.
Another possible problem, you may have your FPGA PCI core
configured in host mode (which can still be a master or target),
and then the IRQ register can not be written.
Cheers,
Dave
next prev parent reply other threads:[~2009-12-03 20:03 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
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 [this message]
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=4B1819AB.1030002@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=iws@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 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).