summaryrefslogtreecommitdiff
path: root/include/acpi
diff options
context:
space:
mode:
authorRafael J. Wysocki <rjw@sisk.pl>2011-01-06 23:34:22 +0100
committerLen Brown <len.brown@intel.com>2011-01-07 01:17:41 -0500
commitf2b56bc808addb908a5bf435d9b942c02af9a7c4 (patch)
tree562c7c96e60505f2b7278add12d19e5a545e7e1b /include/acpi
parentb014f4f1aad3f25d5c7d877a394869645ea0c96b (diff)
downloadlinux-3.10-f2b56bc808addb908a5bf435d9b942c02af9a7c4.tar.gz
linux-3.10-f2b56bc808addb908a5bf435d9b942c02af9a7c4.tar.bz2
linux-3.10-f2b56bc808addb908a5bf435d9b942c02af9a7c4.zip
ACPI / PM: Use device wakeup flags for handling ACPI wakeup devices
There are ACPI devices (buttons and the laptop lid) that can wake up the system from sleep states and have no "physical" companion devices. The ACPI subsystem uses two flags, wakeup.state.enabled and wakeup.flags.always_enabled, for handling those devices, but they are not accessible through the standard device wakeup infrastructure. User space can only control them via the /proc/acpi/wakeup interface that is not really convenient (e.g. the way in which devices are enabled to wake up the system is not portable between different systems, because it requires one to know the devices' "names" used in the system's ACPI tables). To address this problem, use standard device wakeup flags instead of the special ACPI flags for handling those devices. In particular, use device_set_wakeup_capable() to mark the ACPI wakeup devices during initialization and use device_set_wakeup_enable() to allow or disallow them to wake up the system from sleep states. Rework the /proc/acpi/wakeup interface to take these changes into account. Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl> Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'include/acpi')
0 files changed, 0 insertions, 0 deletions