All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Jeremy Higdon <jeremy@sgi.com>
Cc: "Wolstenholme, Daniel E" <daniel.e.wolstenholme@intel.com>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] Add MSI support to sata_vsc driver
Date: Thu, 17 Aug 2006 08:30:45 -0400	[thread overview]
Message-ID: <44E46175.8040501@garzik.org> (raw)
In-Reply-To: <20060817040738.GA854817@sgi.com>

Jeremy Higdon wrote:
> On Tue, Aug 15, 2006 at 05:25:14PM -0700, Wolstenholme, Daniel E wrote:
>>    In the course of some work I'm doing with MSI interrupts, I had an
>>    Intel GD81344 card I wanted to try out with MSI interrupts, and I
>>    found that it does indeed support MSI.  Here's a patch to add support.
> 
> You sent the patch as html.  That's not going to work.  Even the text/plain
> part of it is quoted/printable with lots of extra blank lines, etc.  If
> you're using Outlook, the only way to send a patch is to first turn off
> html and then send the patch as a text/plain attachment (as far as I know).
> 
>>    I implemented this rather simple patch using #ifdef CONFIG_PCI_MSI.  I
>>    noticed some other drivers, such as sata_mv and LSI's fusion drivers,
>>    use a kernel command-line parameter to enable MSI support.  I honestly
>>    don't know the advantage to this; it seems to me to be easier if it's
>>    enabled by default, as long as MSI support is selected in the kernel
>>    configuration.  If not, someone please let me know.
> 
> It might be that some platforms that have MSI enabled won't support it
> on certain machines where these chips are installed.  So it's probably
> best to make it an option.  I'll defer to jgarzik on this, however.

There's no need for #ifdefs at all.  You call pci_enable_msi() 
unconditionally, and if it fails, don't configure/use MSI.  From the 
driver's perspective, everything is handled with runtime function calls.

	Jeff




  reply	other threads:[~2006-08-17 12:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87840E8EE8A8D240A13F8AA92CAB07D9024C14A6@azsmsx402>
2006-08-17  4:07 ` [PATCH] Add MSI support to sata_vsc driver Jeremy Higdon
2006-08-17 12:30   ` Jeff Garzik [this message]
2006-08-17 21:28 Wolstenholme, Daniel E
2006-08-17 23:44 ` Jeff Garzik
2006-08-18  0:18   ` Jeremy Higdon
  -- strict thread matches above, loose matches on Subject: below --
2006-08-23 23:17 Wolstenholme, Daniel E
2006-08-24  6:56 ` Jeff Garzik
2006-08-24 20:55 Wolstenholme, Daniel E
2006-08-25  0:58 Wolstenholme, Daniel E
2006-09-01 20:11 Wolstenholme, Daniel E

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=44E46175.8040501@garzik.org \
    --to=jeff@garzik.org \
    --cc=daniel.e.wolstenholme@intel.com \
    --cc=jeremy@sgi.com \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.