From: MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-pci@vger.kernel.org, greg@kroah.com,
kaneshige.kenji@jp.fujitsu.com
Subject: Re: [PATCH v4] Add pcie_hp=nomsi to disable MSI/MSI-X for pciehp driver
Date: Thu, 26 Jan 2012 11:47:30 -0500 [thread overview]
Message-ID: <4F2183A2.7010007@jp.fujitsu.com> (raw)
In-Reply-To: <CAE9FiQWKRxZcm2FBhP2SxaBGYpROc4grJQtE68OyayPhjQHdsA@mail.gmail.com>
On Thu, 19 Jan 2012 15:41:09 -0800,
Yinghai Lu <yinghai@kernel.org> wrote:
snip
>> Index: linux-3.2/drivers/pci/quirks.c
>> ===================================================================
>> --- linux-3.2.orig/drivers/pci/quirks.c
>> +++ linux-3.2/drivers/pci/quirks.c
>> @@ -2665,6 +2665,35 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AT
>> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, 0x4375,
>> quirk_msi_intx_disable_bug);
>>
>> +/*
>> + * The PCI bridge from Integrated Device Technology(IDT) has a problem
>> + * with MSI/MSI-X.
>> + * An un-wanted interrupt is generated when PCI driver switches from
>> + * MSI/MSI-X to INTx while shutting down the PCI Express port, if it
>> + * provides the Native Hotplug service. The interrupt does not happen
>> + * if MSI/MSI-X is not used on it. Therefore, turn off MSI/MSI-X for
>> + * this device.
>> + */
>> +static void __devinit idt_bridge_msi_disable(struct pci_dev *dev)
>> +{
>> + int pos;
>> + u16 reg16;
>> + u32 reg32;
>> +
>> + pos = pci_pcie_cap(dev);
>> + if (!pos)
>> + return;
>> + pci_read_config_word(dev, pos + PCI_EXP_FLAGS,®16);
>> + if (!(reg16& PCI_EXP_FLAGS_SLOT))
>> + return;
>> + pci_read_config_dword(dev, pos + PCI_EXP_SLTCAP,®32);
>> + if (reg32& PCI_EXP_SLTCAP_HPC) {
>> + pci_msi_off(dev);
>> + dev->no_msi = 1;
>> + }
>> +}
>> +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_IDT, 0x807f, idt_bridge_msi_disable);
>
> do you have statement for IDT, says that is chipset problem ?
I'm trying to contact to them, but not yet.
> it could be your platform fw problem.
>
> if that is the case, you will disable MSI/MSIX for other platform that
> do not have fw problem.
Yinghai,
Btw, how about other pieces? I'm thinking to drop the quirk code
temporary, until I get the comment from them.
Can you give an ACK if I remove the hardware specific quirk code?
Thanks,
Takahiro
next prev parent reply other threads:[~2012-01-26 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 22:32 [PATCH v4] Add pcie_hp=nomsi to disable MSI/MSI-X for pciehp driver MUNEDA Takahiro
2012-01-19 23:41 ` Yinghai Lu
2012-01-24 16:17 ` MUNEDA Takahiro
2012-01-26 16:47 ` MUNEDA Takahiro [this message]
2012-01-26 17:17 ` Yinghai Lu
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=4F2183A2.7010007@jp.fujitsu.com \
--to=muneda.takahiro@jp.fujitsu.com \
--cc=greg@kroah.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox