From: Peter Korsgaard Date: Fri, 22 Oct 2021 12:46:12 +0000 (+0200) Subject: platform/x86: barco-p50-gpio: use KEY_VENDOR for button instead of KEY_RESTART X-Git-Tag: v5.16-rc1~139^2~12 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9527cdff7832b96552ea3cf3fea7f0789fe94e5a;p=thirdparty%2Fkernel%2Flinux.git platform/x86: barco-p50-gpio: use KEY_VENDOR for button instead of KEY_RESTART It turns out that systemd-logind by default listens for KEY_RESTART input events and reboots the machine, which isn't great - So use KEY_VENDOR for the vendor specific identify button instead to not conflict. Signed-off-by: Peter Korsgaard Link: https://lore.kernel.org/r/20211022124612.19780-1-peter@korsgaard.com Signed-off-by: Hans de Goede --- diff --git a/drivers/platform/x86/barco-p50-gpio.c b/drivers/platform/x86/barco-p50-gpio.c index ca0b2564c407b..f5c72e33f9ae3 100644 --- a/drivers/platform/x86/barco-p50-gpio.c +++ b/drivers/platform/x86/barco-p50-gpio.c @@ -101,7 +101,7 @@ static struct gpio_led_platform_data leds_pdata = { /* GPIO keyboard */ static struct gpio_keys_button buttons[] = { { - .code = KEY_RESTART, + .code = KEY_VENDOR, .gpio = P50_GPIO_LINE_BTN, .active_low = 1, .type = EV_KEY,