[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <52B31EDA.60908@compulab.co.il>
Date: Thu, 19 Dec 2013 18:29:14 +0200
From: Denis Turischev <denis.turischev@...pulab.co.il>
To: Sarah Sharp <sarah.a.sharp@...ux.intel.com>
CC: linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: xhci: Switch Intel Lynx Point ports to EHCI on shutdown
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
The bug can be avoided if the USB ports are switched back to EHCI on
shutdown.
Signed-off-by: Denis Turischev <denis@...pulab.co.il>
diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
--- a/drivers/usb/host/xhci-pci.c 2013-12-19 11:36:12.049589400 +0200
+++ b/drivers/usb/host/xhci-pci.c 2013-12-19 11:37:27.261590385 +0200
@@ -91,8 +91,9 @@
xhci->quirks |= XHCI_LPM_SUPPORT;
xhci->quirks |= XHCI_INTEL_HOST;
}
- if (pdev->vendor == PCI_VENDOR_ID_INTEL &&
- pdev->device == PCI_DEVICE_ID_INTEL_PANTHERPOINT_XHCI) {
+ if (pdev->vendor == PCI_VENDOR_ID_INTEL && (
+ (pdev->device == PCI_DEVICE_ID_INTEL_PANTHERPOINT_XHCI) ||
+ (pdev->device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI))) {
xhci->quirks |= XHCI_EP_LIMIT_QUIRK;
xhci->limit_active_eps = 64;
xhci->quirks |= XHCI_SW_BW_CHECKING;
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
--- a/include/linux/pci_ids.h 2013-12-19 11:36:11.945589398 +0200
+++ b/include/linux/pci_ids.h 2013-12-19 11:35:57.817589213 +0200
@@ -2576,6 +2576,7 @@
#define PCI_DEVICE_ID_INTEL_COUGARPOINT_LPC_MAX 0x1c5f
#define PCI_DEVICE_ID_INTEL_PATSBURG_LPC_0 0x1d40
#define PCI_DEVICE_ID_INTEL_PATSBURG_LPC_1 0x1d41
+#define PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI 0x9c31
#define PCI_DEVICE_ID_INTEL_PANTHERPOINT_XHCI 0x1e31
#define PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MIN 0x1e40
#define PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MAX 0x1e5f
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists