summaryrefslogtreecommitdiffstats
path: root/COPYING
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-03-28 11:07:29 +0000
committerBjorn Helgaas <bhelgaas@google.com>2013-04-03 15:49:52 -0600
commit24ad0ef9c8b946ed2abe681e4e44f4a1e643d882 (patch)
tree5fa7bfd81fe811a6ab2f37d0d37593ab71fa68ee /COPYING
parent6e0eda3c389887168455b92b6f7b48f552227067 (diff)
downloadop-kernel-dev-24ad0ef9c8b946ed2abe681e4e44f4a1e643d882.zip
op-kernel-dev-24ad0ef9c8b946ed2abe681e4e44f4a1e643d882.tar.gz
PCI/ACPI: Always resume devices on ACPI wakeup notifications
It turns out that the _Lxx control methods provided by some BIOSes clear the PME Status bit of PCI devices they handle, which means that pci_acpi_wake_dev() cannot really use that bit to check whether or not the device has signalled wakeup. One symptom of the problem is, for example, that when an affected PCI USB controller is runtime-suspended, then plugging in a new USB device into one of the controller's ports will not wake up the controller, which should happen. For this reason, make pci_acpi_wake_dev() always attempt to resume the device it is called for regardless of the device's PME Status bit value (that bit still has to be cleared if set at this point, though). Reported-by: Sarah Sharp <sarah.a.sharp@linux.intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Acked-by: Matthew Garrett <mjg59@srcf.ucam.org> CC: stable@vger.kernel.org # v3.7+
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud