All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: James.Bottomley@HansenPartnership.com, linuxppc-dev@ozlabs.org,
	brking@linux.vnet.ibm.com, wayneb@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/maple: Add a quirk to disable MSI for IPR on Bimini
Date: Fri, 22 May 2009 15:57:52 +1000	[thread overview]
Message-ID: <1242971872.26104.15.camel@pasglop> (raw)
In-Reply-To: <ddac4814a020b7d4248834f846d7a7afe1ce1567.1242968955.git.michael@ellerman.id.au>

On Fri, 2009-05-22 at 15:10 +1000, Michael Ellerman wrote:
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> ---
>  arch/powerpc/platforms/maple/pci.c |   14 ++++++++++++++
>  1 files changed, 14 insertions(+), 0 deletions(-)
> 
> 
> It's getting late in the cycle, so until we can work out what's wrong
> with IPR + MSI on Bimini, add a quirk to disable MSI for IPR.

Thanks, I'll send that to Linus for 2.6.30

Cheers,
Ben.

> diff --git a/arch/powerpc/platforms/maple/pci.c b/arch/powerpc/platforms/maple/pci.c
> index 3018552..04296ff 100644
> --- a/arch/powerpc/platforms/maple/pci.c
> +++ b/arch/powerpc/platforms/maple/pci.c
> @@ -592,3 +592,17 @@ int maple_pci_get_legacy_ide_irq(struct pci_dev *pdev, int channel)
>  	}
>  	return irq;
>  }
> +
> +static void __devinit quirk_ipr_msi(struct pci_dev *dev)
> +{
> +	/* Something prevents MSIs from the IPR from working on Bimini,
> +	 * and the driver has no smarts to recover. So disable MSI
> +	 * on it for now. */
> +
> +	if (machine_is(maple)) {
> +		dev->no_msi = 1;
> +		dev_info(&dev->dev, "Quirk disabled MSI\n");
> +	}
> +}
> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_IBM, PCI_DEVICE_ID_IBM_OBSIDIAN,
> +			quirk_ipr_msi);

      reply	other threads:[~2009-05-22  5:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22  5:10 [PATCH] powerpc/maple: Add a quirk to disable MSI for IPR on Bimini Michael Ellerman
2009-05-22  5:57 ` Benjamin Herrenschmidt [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=1242971872.26104.15.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=wayneb@linux.vnet.ibm.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.