summaryrefslogtreecommitdiff
path: root/include/uapi/linux
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2014-07-14 22:41:41 +0200
committerLuis Henriques <luis.henriques@canonical.com>2015-01-16 14:34:52 +0000
commit79d914f5fe330ffbeb578c03560bb7a80252832d (patch)
treedec0cd435ff7a7c482c9f74873b9c65ba8fe34e7 /include/uapi/linux
parent3f5153776817e63f6ddf61138f73738637dbd55f (diff)
ACPI / scan: No implicit wake notification for buttons
commit bd9b2f9aff26c185c1f8e0cd08a850ee4ace391a upstream. 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> Cc: Joseph Salisbury <joseph.salisbury@canonical.com> Signed-off-by: Luis Henriques <luis.henriques@canonical.com>
Diffstat (limited to 'include/uapi/linux')
0 files changed, 0 insertions, 0 deletions