summaryrefslogtreecommitdiffstats
path: root/drivers/acpi/device_pm.c
diff options
context:
space:
mode:
authorAaron Lu <aaron.lu@intel.com>2012-11-21 23:33:40 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2012-11-21 23:33:40 +0100
commit1399dfcdfe89898ccd791216f9679ba734aea910 (patch)
tree294a90abd00a3a293ea80419782aa690c788102c /drivers/acpi/device_pm.c
parentddc150f7a33ae0c9cb16eaac3641abc00f56316f (diff)
downloadop-kernel-dev-1399dfcdfe89898ccd791216f9679ba734aea910.zip
op-kernel-dev-1399dfcdfe89898ccd791216f9679ba734aea910.tar.gz
ACPI / PM: Introduce os_accessible flag for power_state
Currently we have valid flag to represent if this ACPI device power state is valid. A device power state is valid does not necessarily mean we, as OSPM, has a mean to put the device into that power state, e.g. D3 cold is always a valid power state for any ACPI device, but if there is no _PS3 or _PRx for this device, we can't really put that device into D3 cold power state. The same is true for D0 power state. So here comes the os_accessible flag, which is only set if the device has provided us the required means to put it into that power state, e.g. if we have _PS3 or _PRx, we can put the device into D3 cold state and thus, D3 cold power state's os_accessible flag will be set in this case. And a new wrapper inline function is added to be used to check if firmware has provided us a way to power off the device during runtime. Signed-off-by: Aaron Lu <aaron.lu@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/acpi/device_pm.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud