All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Andy Yan <ayan@marvell.com>
Cc: james.bottomley@hansenpartnership.com, jeff@garzik.org,
	linux-scsi@vger.kernel.org, jfeng@marvell.com,
	qswang@marvell.com
Subject: Re: [PATCH 2/7]MVSAS:add supporting MSI feature
Date: Sat, 14 Nov 2009 15:56:27 -0700	[thread overview]
Message-ID: <20091114225627.GK16033@parisc-linux.org> (raw)
In-Reply-To: <20091109120818.GA32336@Andy.marvell.com>

On Mon, Nov 09, 2009 at 08:08:18PM +0800, Andy Yan wrote:
> +void mvs_enable_msi(struct mvs_info *mvi)
> +{
> +	u32 tmp;
> +	pci_read_config_dword(mvi->pdev, PCR_CMD, &tmp);
> +	tmp |= 1 << 10;    	/* disable interrupt */
> +	pci_write_config_dword(mvi->pdev, PCR_CMD, tmp);

What makes you think the pci_enable_msi() code doesn't set this bit?

> +	pci_read_config_dword(mvi->pdev, PCR_MSI_CTRL, &tmp);
> +	tmp |= 1 << 16; 		/* enable MSI */
> +	pci_write_config_dword(mvi->pdev, PCR_MSI_CTRL, tmp);

... and what makes you think it doesn't set this bit either?

> +static ssize_t
> +mvs_show_driver_version(struct device *cdev,
> +			struct device_attribute *attr,
> +			char *buffer)
> +{
> +	return snprintf(buffer, PAGE_SIZE, "%s\n", DRV_VERSION);
> +}

There's a lot of code in this patch not related to enabling MSI.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

      parent reply	other threads:[~2009-11-14 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 12:08 [PATCH 2/7]MVSAS:add supporting MSI feature Andy Yan
2009-11-14 18:19 ` James Bottomley
2009-11-14 22:56 ` Matthew Wilcox [this message]

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=20091114225627.GK16033@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=ayan@marvell.com \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=jeff@garzik.org \
    --cc=jfeng@marvell.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=qswang@marvell.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 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.