diff options
| author | Kai-Heng Feng <kai.heng.feng@canonical.com> | 2019-09-02 22:52:52 +0800 |
|---|---|---|
| committer | Bjorn Helgaas <bhelgaas@google.com> | 2019-11-21 07:49:31 -0600 |
| commit | 7e8ce0e2b036dbc6617184317983aea4f2c52099 (patch) | |
| tree | 9afaf1a703976e947d37653a03088923912287f2 /arch/nios2/include | |
| parent | bbd8810d399812f2016713565e4d8ff8f1508aa6 (diff) | |
| download | linux-stable-7e8ce0e2b036dbc6617184317983aea4f2c52099.tar.gz linux-stable-7e8ce0e2b036dbc6617184317983aea4f2c52099.tar.bz2 linux-stable-7e8ce0e2b036dbc6617184317983aea4f2c52099.zip | |
x86/PCI: Avoid AMD FCH XHCI USB PME# from D0 defect
The AMD FCH USB XHCI Controller advertises support for generating PME#
while in D0. When in D0, it does signal PME# for USB 3.0 connect events,
but not for USB 2.0 or USB 1.1 connect events, which means the controller
doesn't wake correctly for those events.
00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7914] (rev 20) (prog-if 30 [XHCI])
Subsystem: Dell FCH USB XHCI Controller [1028:087e]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Clear PCI_PM_CAP_PME_D0 in dev->pme_support to indicate the device will not
assert PME# from D0 so we don't rely on it.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203673
Link: https://lore.kernel.org/r/20190902145252.32111-1-kai.heng.feng@canonical.com
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Cc: stable@vger.kernel.org
Diffstat (limited to 'arch/nios2/include')
0 files changed, 0 insertions, 0 deletions