Commit f57a98e1 authored by Thinh Nguyen's avatar Thinh Nguyen Committed by Bjorn Helgaas

PCI: Work around Synopsys duplicate Device ID (HAPS USB3, NXP i.MX)

There are at least four different parts with the same Vendor and Device
ID ([16c3:abcd]):

  1) Synopsys HAPS USB3 controller
  2) Synopsys PCIe Root Port in Freescale/NXP i.MX6Q (reported by Lucas)
  3) Synopsys PCIe Root Port in Freescale/NXP i.MX6QP (reported by Lukas)
  4) Synopsys PCIe Root Port in Freescale/NXP i.MX7D (reported by Trent)

The HAPS USB3 controller has a Class Code of PCI_CLASS_SERIAL_USB_XHCI,
which means the XHCI driver would normally claim it.  Previously,
quirk_synopsys_haps() changed the Class Code of all [16c3:abcd] devices,
including the Root Ports, to PCI_CLASS_SERIAL_USB_DEVICE to prevent the
XHCI driver from claiming them so dwc3-haps can claim them instead.

Changing the Class Code of the Root Ports prevents the PCI core from
handling them as bridges, so devices below them don't work.

Restrict the quirk so it only changes the Class Code for devices that start
with the PCI_CLASS_SERIAL_USB_XHCI Class Code, leaving the Root Ports
alone.

Fixes: 03e67425 ("PCI: Override Synopsys USB 3.x HAPS device class")
Reported-by: default avatarLukas F. Hartmann <lukas@mntmn.com>
Reported-by: default avatarTrent Piepho <tpiepho@impinj.com>
Reported-by: default avatarLucas Stach <l.stach@pengutronix.de>
Signed-off-by: default avatarThinh Nguyen <thinhn@synopsys.com>
[bhelgaas: changelog]
Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
parent f14bcc0a
...@@ -639,8 +639,9 @@ static void quirk_synopsys_haps(struct pci_dev *pdev) ...@@ -639,8 +639,9 @@ static void quirk_synopsys_haps(struct pci_dev *pdev)
break; break;
} }
} }
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_SYNOPSYS, PCI_ANY_ID, DECLARE_PCI_FIXUP_CLASS_HEADER(PCI_VENDOR_ID_SYNOPSYS, PCI_ANY_ID,
quirk_synopsys_haps); PCI_CLASS_SERIAL_USB_XHCI, 0,
quirk_synopsys_haps);
/* /*
* Let's make the southbridge information explicit instead of having to * Let's make the southbridge information explicit instead of having to
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment