From: Magnus Damm <magnus.damm@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 08/08] ARM: shmobile: Add Koelsch SW2 support
Date: Tue, 08 Oct 2013 03:40:08 +0000 [thread overview]
Message-ID: <20131008034008.20455.77595.sendpatchset@w520> (raw)
In-Reply-To: <20131008033851.20455.68845.sendpatchset@w520>
From: Magnus Damm <damm@opensource.se>
Enable Koelsch GPIO switch for GPIO input and IRQ testing purpose.
Signed-off-by: Magnus Damm <damm@opensource.se>
---
arch/arm/mach-shmobile/board-koelsch.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
--- 0012/arch/arm/mach-shmobile/board-koelsch.c
+++ work/arch/arm/mach-shmobile/board-koelsch.c 2013-10-07 14:05:22.000000000 +0900
@@ -19,6 +19,9 @@
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/
+#include <linux/gpio.h>
+#include <linux/gpio_keys.h>
+#include <linux/input.h>
#include <linux/kernel.h>
#include <linux/leds.h>
#include <linux/platform_data/gpio-rcar.h>
@@ -51,6 +54,22 @@ static const struct gpio_led_platform_da
.num_leds = ARRAY_SIZE(koelsch_leds),
};
+/* GPIO KEY */
+#define GPIO_KEY(c, g, d, ...) \
+ { .code = c, .gpio = g, .desc = d, .active_low = 1 }
+
+static struct gpio_keys_button gpio_buttons[] = {
+ GPIO_KEY(KEY_4, RCAR_GP_PIN(5, 3), "SW2-pin4"),
+ GPIO_KEY(KEY_3, RCAR_GP_PIN(5, 2), "SW2-pin3"),
+ GPIO_KEY(KEY_2, RCAR_GP_PIN(5, 1), "SW2-pin2"),
+ GPIO_KEY(KEY_1, RCAR_GP_PIN(5, 0), "SW2-pin1"),
+};
+
+static const struct gpio_keys_platform_data koelsch_keys_pdata __initconst = {
+ .buttons = gpio_buttons,
+ .nbuttons = ARRAY_SIZE(gpio_buttons),
+};
+
static void __init koelsch_add_standard_devices(void)
{
r8a7791_clock_init();
@@ -59,6 +78,9 @@ static void __init koelsch_add_standard_
platform_device_register_data(&platform_bus, "leds-gpio", -1,
&koelsch_leds_pdata,
sizeof(koelsch_leds_pdata));
+ platform_device_register_data(&platform_bus, "gpio-keys", -1,
+ &koelsch_keys_pdata,
+ sizeof(koelsch_keys_pdata));
}
static const char * const koelsch_boards_compat_dt[] __initconst = {
next prev parent reply other threads:[~2013-10-08 3:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 3:38 [PATCH 00/08] ARM: shmobile: r8a7791 and Koelsch GPIO/PFC support Magnus Damm
2013-10-08 3:39 ` [PATCH 01/08] ARM: shmobile: r8a7791 PFC device tree node Magnus Damm
2013-10-09 2:02 ` Simon Horman
2013-10-08 3:39 ` [PATCH 02/08] ARM: shmobile: r8a7791 PFC platform device support Magnus Damm
2013-10-09 2:02 ` Simon Horman
2013-10-08 3:39 ` [PATCH 03/08] ARM: shmobile: Select GPIO in case of the r8a7791 SoC Magnus Damm
2013-10-09 2:02 ` Simon Horman
2013-10-08 3:39 ` [PATCH 04/08] ARM: shmobile: r8a7791 GPIO device tree node Magnus Damm
2013-10-09 2:03 ` Simon Horman
2013-10-08 3:39 ` [PATCH 05/08] ARM: shmobile: r8a7791 GPIO platform device support Magnus Damm
2013-10-09 2:03 ` Simon Horman
2013-10-09 2:05 ` Simon Horman
2013-10-08 3:39 ` [PATCH 06/08] ARM: shmobile: Enable PFC/GPIO on the Koelsch board Magnus Damm
2013-10-09 2:32 ` Simon Horman
2013-10-08 3:39 ` [PATCH 07/08] ARM: shmobile: Add Koelsch LED6, LED7 and LED8 support Magnus Damm
2013-10-09 2:13 ` Simon Horman
2013-10-09 2:32 ` Simon Horman
2013-10-08 3:40 ` Magnus Damm [this message]
2013-10-09 2:33 ` [PATCH 08/08] ARM: shmobile: Add Koelsch SW2 support Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131008034008.20455.77595.sendpatchset@w520 \
--to=magnus.damm@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).