summaryrefslogtreecommitdiffstats
path: root/arch/x86/pci
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-06-23 14:58:11 +0200
committerBjorn Helgaas <bhelgaas@google.com>2017-06-30 11:15:12 -0500
commit666ff6f83e1db6ed847abf44eb5e3402d82b9350 (patch)
treedec4eb16de07ce72cb5d0119e6cdeebe0cc7bd4b /arch/x86/pci
parent0bf3730bbc41f155543fa63becb4ff436d6a00a9 (diff)
downloadop-kernel-dev-666ff6f83e1db6ed847abf44eb5e3402d82b9350.zip
op-kernel-dev-666ff6f83e1db6ed847abf44eb5e3402d82b9350.tar.gz
PCI/PM: Avoid using device_may_wakeup() for runtime PM
pci_target_state() calls device_may_wakeup() which checks whether or not the device may wake up the system from sleep states, but pci_target_state() is used for runtime PM too. Since runtime PM is expected to always enable remote wakeup if possible, modify pci_target_state() to take additional argument indicating whether or not it should look for a state from which the device can signal wakeup and pass either the return value of device_can_wakeup(), or "false" (if the device itself is not wakeup-capable) to it from the code related to runtime PM. While at it, fix the comment in pci_dev_run_wake() which is not about sleep states. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'arch/x86/pci')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud