From: Roland Dreier <rdreier@cisco.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>
Subject: Re: MSI and driver APIs
Date: Thu, 15 Dec 2005 13:36:37 -0800 [thread overview]
Message-ID: <adawti6m49m.fsf@cisco.com> (raw)
In-Reply-To: <1134681498.16880.39.camel@gaston> (Benjamin Herrenschmidt's message of "Fri, 16 Dec 2005 08:18:17 +1100")
Benjamin> But won't the driver call pci_enable/disable_msi() in
Benjamin> those cases ? If not, it's easy enough to add (explicit
Benjamin> disable rather than not-enabled).
Benjamin> I'm mostly concerned about "dumb" drivers that don't
Benjamin> know about MSI at all...
Well, a driver for a chip that does MSI may be "dumb" in that sense.
For example, tg3 only got MSI support in April '05 or so.
Although looking at tg3.c, it seems that nothing special is required
to disable MSI -- there is a special chip register bit to set to
enable MSI mode, but it doesn't seem necessary to clear the bit to
disable MSI.
The case I'm worried about is a chip where something special has to be
done to get out of MSI mode, but the driver is totally dumb and just
does request_irq() on its legacy interrupt. The core PCI code doesn't
have the chip-specific knowledge to fully turn off MSI.
But I don't know of a real device that falls into that category, so
your scheme is probably OK.
- R.
next prev parent reply other threads:[~2005-12-15 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 3:38 MSI and driver APIs Benjamin Herrenschmidt
2005-12-15 21:07 ` Roland Dreier
2005-12-15 21:08 ` Benjamin Herrenschmidt
2005-12-15 21:18 ` Roland Dreier
2005-12-15 21:18 ` Benjamin Herrenschmidt
2005-12-15 21:36 ` Roland Dreier [this message]
2005-12-15 21:42 ` David S. Miller
2005-12-15 21:56 ` Benjamin Herrenschmidt
2005-12-16 0:51 ` Greg KH
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=adawti6m49m.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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