summaryrefslogtreecommitdiffstats
path: root/drivers/acpi/processor_core.c
diff options
context:
space:
mode:
authorRafael J. Wysocki2014-07-14 22:41:41 +0200
committerRafael J. Wysocki2014-07-23 23:13:19 +0200
commitbd9b2f9aff26c185c1f8e0cd08a850ee4ace391a (patch)
treed566da1fdad50aad82a8538e626827c1fe44ae21 /drivers/acpi/processor_core.c
parentMerge branch 'acpica' into acpi-gpe (diff)
downloadkernel-qcow2-linux-bd9b2f9aff26c185c1f8e0cd08a850ee4ace391a.tar.gz
kernel-qcow2-linux-bd9b2f9aff26c185c1f8e0cd08a850ee4ace391a.tar.xz
kernel-qcow2-linux-bd9b2f9aff26c185c1f8e0cd08a850ee4ace391a.zip
ACPI / scan: No implicit wake notification for buttons
The ACPI device enumeration code in Linux assumes that buttons always are wakeup devices, so it calls acpi_setup_gpe_for_wake() for them which leads to undesirable side effects. Namely, that function sets up implicit device wake notification mechanism for a given GPE if there is no handler method in the ACPI namespace, which from the ACPICA's perspective means that there always is a way to handle that GPE if enabled. However, we don't handle wake notify events for buttons, so if there are no handler methods for their GPEs in the namespace, enabling a button GPE at run time leads to a GPE storm in some cases (the GPE triggers, ACPICA carries out the implicit wake notification for it which isn't handled, so the GPE triggers again and so on). To prevent that from happening use acpi_mark_gpe_for_wake() instead of acpi_setup_gpe_for_wake() for buttons which will cause ACPICA to only enable button GPEs if there are handler methods for the in the namespace. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/acpi/processor_core.c')
0 files changed, 0 insertions, 0 deletions