linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <alberto.vignani@fastwebnet.it>
To: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
	<johan@kernel.org>, <linux-usb@vger.kernel.org>
Cc: <andriy.shevchenko@linux.intel.com>
Subject: R: [PATCH v2 1/2] PCI: Disable MSI for Pericom PCIe-USB adapter
Date: Fri, 6 Nov 2020 16:34:25 +0100 (CET)	[thread overview]
Message-ID: <33436598.119601604676865427.JavaMail.root@pr006msr> (raw)

Tested-by: alberto.vignani@fastwebnet.it

>----Messaggio originale----
>Da: andriy.shevchenko@linux.intel.com
>Data: 06/11/2020 11.05
>A: "Bjorn Helgaas"<bhelgaas@google.com>, <linux-pci@vger.kernel.org>, <johan@ke
rnel.org>, <linux-usb@vger.kernel.org>
>Cc: "Andy Shevchenko"<andriy.shevchenko@linux.intel.com>, <alberto.vignani@fast
webnet.it>
>Ogg: [PATCH v2 1/2] PCI: Disable MSI for Pericom PCIe-USB adapter
>
>Pericom PCIe-USB adapter advertises MSI, but documentation says
>"The MSI Function is not implemented on this device." in the chapters
>7.3.27, 7.3.29-7.3.31.
>
>Fixes: 306c54d0edb6 ("usb: hcd: Try MSI interrupts on PCI devices")
>Datasheet: https://www.diodes.com/assets/Datasheets/PI7C9X440SL.pdf
>Reported-by: alberto.vignani@fastwebnet.it
>Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>---
>v2: dropped confusing word (David), added ifdeffery (Ben)
> drivers/pci/quirks.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
>diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
>index f70692ac79c5..e66e0cc8f99b 100644
>--- a/drivers/pci/quirks.c
>+++ b/drivers/pci/quirks.c
>@@ -5567,17 +5567,26 @@ static void pci_fixup_no_d0_pme(struct pci_dev *dev)
> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ASMEDIA, 0x2142, pci_fixup_no_d0_pme);
> 
> /*
>- * Device [12d8:0x400e] and [12d8:0x400f]
>+ * Device 12d8:0x400e [OHCI] and 12d8:0x400f [EHCI]
>+ *
>  * These devices advertise PME# support in all power states but don't
>  * reliably assert it.
>+ *
>+ * These devices advertise MSI, but documentation (PI7C9X440SL.pdf) says
>+ * "The MSI Function is not implemented on this device." in the chapters
>+ * 7.3.27, 7.3.29-7.3.31.
>  */
>-static void pci_fixup_no_pme(struct pci_dev *dev)
>+static void pci_fixup_no_msi_no_pme(struct pci_dev *dev)
> {
>+#ifdef CONFIG_PCI_MSI
>+	pci_info(dev, "The MSI is not implemented on this device, disabling it\n");
>+	dev->no_msi = 1;
>+#endif
> 	pci_info(dev, "PME# is unreliable, disabling it\n");
> 	dev->pme_support = 0;
> }
>-DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_PERICOM, 0x400e, pci_fixup_no_pme);
>-DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_PERICOM, 0x400f, pci_fixup_no_pme);
>+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_PERICOM, 0x400e, pci_fixup_no_msi_no_pme
);
>+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_PERICOM, 0x400f, pci_fixup_no_msi_no_pme
);
> 
> static void apex_pci_fixup_class(struct pci_dev *pdev)
> {
>-- 
>2.28.0





             reply	other threads:[~2020-11-06 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 15:34 alberto.vignani [this message]
2020-11-09 12:07 ` R: [PATCH v2 1/2] PCI: Disable MSI for Pericom PCIe-USB adapter Andy Shevchenko

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=33436598.119601604676865427.JavaMail.root@pr006msr \
    --to=alberto.vignani@fastwebnet.it \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=johan@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).