On Mon, Oct 30, 2017 at 06:40:49PM +0100, Hans de Goede wrote: > In some cases it is undesirable for a wakeup button to send input events > to userspace if pressed to wakeup the system (if pressed during suspend). > > A typical example of this is the power-button on laptops / tablets, > sending a KEY_POWER event to userspace when woken up with the power-button > will cause userspace to immediately suspend the system again which is > undesirable. > > For power-buttons attached to a PMIC, or handled by e.g. ACPI, not sending > an input event in this case is take care of by the PMIC / ACPI hardware / > code. But in the case of a GPIO button we need to explicitly suppress the > sending of the input event. > > This commit supports this by adding a suppress_evdev_events_on_wakeup bool > to struct gpio_keys_button, which platform code can set to suppress the > input events for presses of wakeup keys during suspend. I think this is [your] userspace issue. What if I press the button rapidly several times? I know Android actually _wants_ to see KEY_POWER at resume, or its opportunistic suspend will kick in right away. I think ChromeOS is OK with getting KEY_POWER on resume as well. I'd say you need to have a small timeout before you start suspending again. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
