mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-19 02:34:01 +08:00
6ad16b78a0
EC_MKBP_EVENT_SENSOR_FIFO events can be triggered for a variety of reasons, and there are very few cases in which they should be treated as wakeup interrupts (particularly, when a certain MOTIONSENSE_MODULE_FLAG_* is set, but this is not even supported in the mainline cros_ec_sensor driver yet). Most of the time, they are benign sensor readings. In any case, the top-level cros_ec device doesn't know enough to determine that they should wake the system, and so it should not report the event. This would be the job of the cros_ec_sensors driver to parse. This patch adds checks to cros_ec_get_next_event() such that it doesn't signal 'wakeup' for events of type EC_MKBP_EVENT_SENSOR_FIFO. This patch is particularly relevant on devices like Scarlet (Rockchip RK3399 tablet, known as Acer Chromebook Tab 10), where the EC firmware reports sensor events much more frequently. This was causing /sys/power/wakeup_count to increase very frequently, often needlessly interrupting our ability to suspend the system. Signed-off-by: Brian Norris <briannorris@chromium.org> Signed-off-by: Benson Leung <bleung@chromium.org> |
||
|---|---|---|
| .. | ||
| chromeos_laptop.c | ||
| chromeos_pstore.c | ||
| chromeos_tbmc.c | ||
| cros_ec_debugfs.c | ||
| cros_ec_i2c.c | ||
| cros_ec_lightbar.c | ||
| cros_ec_lpc_mec.c | ||
| cros_ec_lpc_mec.h | ||
| cros_ec_lpc_reg.c | ||
| cros_ec_lpc_reg.h | ||
| cros_ec_lpc.c | ||
| cros_ec_proto.c | ||
| cros_ec_spi.c | ||
| cros_ec_sysfs.c | ||
| cros_ec_vbc.c | ||
| cros_kbd_led_backlight.c | ||
| Kconfig | ||
| Makefile | ||