From: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>
The ACPI_FADT_LOW_POWER_S0 flag merely means that it is better to
use low-power S0 idle on the given platform than S3 (provided that
the latter is supported) and it doesn't preclude using either of
them (which of them will be used depends on the choices made by user
space).
Because of that, ACPI_FADT_LOW_POWER_S0 is generally not sufficient
for making decisions in device drivers and so i2c_hid_acpi_probe()
should not use it.
Moreover, Linux always supports suspend-to-idle, so if a given
device can wake up the system from suspend-to-idle, then it can be
marked as wakeup capable unconditionally, so make that happen in
i2c_hid_acpi_probe().
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>
---
drivers/hid/i2c-hid/i2c-hid-acpi.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
Index: linux-pm/drivers/hid/i2c-hid/i2c-hid-acpi.c
===================================================================
--- linux-pm.orig/drivers/hid/i2c-hid/i2c-hid-acpi.c
+++ linux-pm/drivers/hid/i2c-hid/i2c-hid-acpi.c
@@ -105,10 +105,8 @@ static int i2c_hid_acpi_probe(struct i2c
acpi_device_fix_up_power(adev);
- if (acpi_gbl_FADT.flags & ACPI_FADT_LOW_POWER_S0) {
- device_set_wakeup_capable(dev, true);
- device_set_wakeup_enable(dev, false);
- }
+ device_set_wakeup_capable(dev, true);
+ device_set_wakeup_enable(dev, false);
return i2c_hid_core_probe(client, &ihid_acpi->ops,
hid_descriptor_address, 0);
