[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190704090205.19400-4-fe@dev.tdt.de>
Date: Thu, 4 Jul 2019 11:02:05 +0200
From: Florian Eckert <fe@....tdt.de>
To: Eckert.Florian@...glemail.com, info@...ux.net,
dvhart@...radead.org, andy@...radead.org
Cc: platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
Florian Eckert <fe@....tdt.de>
Subject: [PATCH 3/3] platform//x86/pcengines-apuv2: update gpio button definition
* Add the gpio number, so the button subsystem can find the right gpio.
* Change also the keycode from KEY_SETUP to KEY_RESTART, because it
seems more expressive to me and in the Alix-Board, which is the
predecessor, there isthis keycode defined too. I think this is also
intended by Pcengines. Also many embedded systems defined in the kernel
use this key code as well.
Signed-off-by: Florian Eckert <fe@....tdt.de>
---
drivers/platform/x86/pcengines-apuv2.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/platform/x86/pcengines-apuv2.c b/drivers/platform/x86/pcengines-apuv2.c
index d50a50e9d34c..370fd2686d59 100644
--- a/drivers/platform/x86/pcengines-apuv2.c
+++ b/drivers/platform/x86/pcengines-apuv2.c
@@ -116,7 +116,8 @@ struct gpiod_lookup_table gpios_led_table = {
static struct gpio_keys_button apu2_keys_buttons[] = {
{
- .code = KEY_SETUP,
+ .code = KEY_RESTART,
+ .gpio = 508,
.active_low = 1,
.desc = "front button",
.type = EV_KEY,
--
2.11.0
Powered by blists - more mailing lists