From: Mark Lord <liml@rtr.ca>
To: michael@ellerman.id.au
Cc: Grant Grundler <grundler@google.com>,
Daniel Barkalow <barkalow@iabervon.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
linux-pci@vger.kernel.org
Subject: Re: libata, devm_*, and MSI ?
Date: Wed, 21 Jan 2009 10:05:03 -0500 [thread overview]
Message-ID: <4977399F.7000104@rtr.ca> (raw)
In-Reply-To: <1232511378.11241.64.camel@localhost>
Michael Ellerman wrote:
> On Tue, 2009-01-20 at 20:02 -0800, Grant Grundler wrote:
..
>> 1) post lspci -v output to verify device (and bridges) is programmed correctly.
>> 2) look for chipset quirks that disable global msi
>
> The kernel shouldn't let you enable MSI if that's the case, ie.
> pci_enable_msi() should fail.
..
Exactly. So it shouldn't be that, then.
> It might still be worth looking at the quirks though, in case there's
> one for a previous revision of your bridge or something.
>
>> 3) Make sure MMIO ranges for 0xfee00000 are routed to local APIC
>> ie each bridge needs to route that address somehow (negative decode
>> is common for upstream).
>> 4) manually trigger the MSI by doing a MMIO write to the correct
>> 0xfee00000 address with the assigned vector in order to see if your
>> interrupt handler gets called.
>
> And can you plug something directly into the PCIe bus? If so does MSI
> work on that?
..
Yup. PCIe cards have no problem with MSI in that box.
More later..
next prev parent reply other threads:[~2009-01-21 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 16:03 libata, devm_*, and MSI ? Mark Lord
2009-01-20 16:07 ` Mark Lord
2009-01-20 17:44 ` Grant Grundler
2009-01-20 18:16 ` Mark Lord
2009-01-20 18:51 ` Grant Grundler
2009-01-20 19:54 ` Mark Lord
2009-01-21 11:59 ` Tejun Heo
2009-01-20 21:50 ` Daniel Barkalow
2009-01-21 3:39 ` Mark Lord
2009-01-21 4:02 ` Grant Grundler
2009-01-21 4:16 ` Michael Ellerman
2009-01-21 15:05 ` Mark Lord [this message]
2009-01-22 0:33 ` Robert Hancock
2009-01-23 18:11 ` Mark Lord
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=4977399F.7000104@rtr.ca \
--to=liml@rtr.ca \
--cc=barkalow@iabervon.org \
--cc=grundler@google.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michael@ellerman.id.au \
/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).