summaryrefslogtreecommitdiffstats
path: root/drivers/infiniband/hw/cxgb4
diff options
context:
space:
mode:
authorRafael J. Wysocki <rjw@sisk.pl>2012-05-29 21:21:07 +0200
committerRafael J. Wysocki <rjw@sisk.pl>2012-05-29 21:21:07 +0200
commitdbe9a2edd17d843d80faf2b99f20a691c1853418 (patch)
treecdb93bb64452b6e60ffd8ca1ceea75716a1e9f64 /drivers/infiniband/hw/cxgb4
parent38c92fff988d518fe80dc23d0d44d66bd7e47ddd (diff)
downloadlinux-stable-dbe9a2edd17d843d80faf2b99f20a691c1853418.tar.gz
linux-stable-dbe9a2edd17d843d80faf2b99f20a691c1853418.tar.bz2
linux-stable-dbe9a2edd17d843d80faf2b99f20a691c1853418.zip
ACPI / PM: Make acpi_pm_device_sleep_state() follow the specification
The comparison between the system sleep state being entered and the lowest system sleep state the given device may wake up from in acpi_pm_device_sleep_state() is reversed, because the specification (ACPI 5.0) says that for wakeup to work: "The sleeping state being entered must be less than or equal to the power state declared in element 1 of the _PRW object." In other words, the state returned by _PRW is the deepest (lowest-power) system sleep state the device is capable of waking up the system from. Moreover, acpi_pm_device_sleep_state() also should check if the wakeup capability is supported through ACPI, because in principle it may be done via native PCIe PME, for example, in which case _SxW should not be evaluated. Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'drivers/infiniband/hw/cxgb4')
0 files changed, 0 insertions, 0 deletions