From: Grant Grundler <grundler@google.com>
To: Mark Lord <liml@rtr.ca>
Cc: "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: Tue, 20 Jan 2009 10:51:47 -0800 [thread overview]
Message-ID: <da824cf30901201051v66ae13c4i3476097ee31db281@mail.gmail.com> (raw)
In-Reply-To: <497614F5.6000301@rtr.ca>
On Tue, Jan 20, 2009 at 10:16 AM, Mark Lord <liml@rtr.ca> wrote:
...
>> I don't think that's necessary if free_irq() or disable_irq() are called.
>> However, I'm not seeing those get called either.
...
> The linux/Documentation/PCI/MSI-HOWTO.txt information is rather explicit
> about it, and the pci core code does seem to expect it.
It looks like pci_disable_msi() requires free_irq() to be called first in order
to guarantee the vectors are no longer in use. But I didn't see any code to
enforce that. Which code was "expecting free_irq()" to be called?
I've learned that anything in Documentation/ is explicit - and sometimes stale
and/or just missing (like you are rediscovering). Two years ago I took a whack
at Documentation/PCI/pci.txt and it's probably time to revisit that again and
add references to pci_intx().
> Those calls to pci_intx() are definitely redundant,
> as the pci core already does that for us on the relevant paths.
True. Want to submit a patch to remove the redundant code?
>
>>> Perhaps somebody from the PCI side of things might enlighten us all.
>>
>> http://lists.linuxcoding.com/kernel/2005-q3/msg11296.html
>>
>> Shows when pci_intx() was added. linux-pci was NOT cc'd on that email.
>> And no one asked for Documentation/ update. C'est la vie.
>
> ..
>
> I still think the documentation matches the code in the pci core, though.
Yeah, I think you are right.
grant
>
> Patch for sata_mv coming shortly.
>
> Cheers
>
next prev parent reply other threads:[~2009-01-20 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 16:03 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 [this message]
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
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=da824cf30901201051v66ae13c4i3476097ee31db281@mail.gmail.com \
--to=grundler@google.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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
Powered by JetHome