From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Roland Dreier <rdreier@cisco.com>
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: Fri, 16 Dec 2005 08:08:02 +1100 [thread overview]
Message-ID: <1134680882.16880.37.camel@gaston> (raw)
In-Reply-To: <adamzj2nk76.fsf@cisco.com>
> It seems OK to me to say that a driver's probe routine could be called
> with MSI enabled. A naive driver would just use the irq number from
> the PCI device struct and never care whether interrupts were INTx or
> MSI. This does fall down for hardware like tg3, where something
> beyond the simple PCI header manipulation is required to turn on MSI use.
>
> Full MSI-X would be much harder to handle transparently, since
> handling multiple different interrupts typically requires a lot more
> logic in the driver.
You can have multiple MSIs too (they just have to be contiguous in
numbers and aligned on the nearest power of 2).
I'm tempted to leave them enabled and only disable them when
request_irq() is done on the legacy INTx... Does anybody see a problem
with this approach ?
Ben.
next prev parent reply other threads:[~2005-12-15 21:12 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 [this message]
2005-12-15 21:18 ` Roland Dreier
2005-12-15 21:18 ` Benjamin Herrenschmidt
2005-12-15 21:36 ` Roland Dreier
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=1134680882.16880.37.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=rdreier@cisco.com \
/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