diff options
| author | Peter Korsgaard <peter.korsgaard@barco.com> | 2021-10-22 14:46:12 +0200 |
|---|---|---|
| committer | Hans de Goede <hdegoede@redhat.com> | 2021-10-24 10:17:46 +0200 |
| commit | 9527cdff7832b96552ea3cf3fea7f0789fe94e5a (patch) | |
| tree | 84170b59a58aa12085be67c84d5715af5a4a66e9 /drivers/platform | |
| parent | c4b9ad6bf99007f67a4d0bbd83fd15d1bdd0222f (diff) | |
| download | linux-9527cdff7832b96552ea3cf3fea7f0789fe94e5a.tar.bz2 | |
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 <peter.korsgaard@barco.com>
Link: https://lore.kernel.org/r/20211022124612.19780-1-peter@korsgaard.com
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Diffstat (limited to 'drivers/platform')
| -rw-r--r-- | drivers/platform/x86/barco-p50-gpio.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/platform/x86/barco-p50-gpio.c b/drivers/platform/x86/barco-p50-gpio.c index ca0b2564c407..f5c72e33f9ae 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, |