From: Daniel Mack <daniel@caiaq.de>
To: Richard Purdie <rpurdie@rpsys.net>, linux-kernel@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, Constantin Baranov <const@mimas.ru>
Subject: [PATCH] leds-alix2: add support for button connected to J15
Date: Fri, 16 Oct 2009 15:03:15 +0200 [thread overview]
Message-ID: <20091016130315.GT28832@buzzloop.caiaq.de> (raw)
Hi,
for a project I was working on, we used the J15 connector of the ALIX.2D
board (which is connected to a GPIO of the CS5536 Geode companion chip)
for an external button switch.
I thought it might be worth sharing this piece of code, so others can do
the same.
There is, however, a small hardware modification is necessary as the pin
is also shared as buzzer output. I noted that in the Kconfig entry.
The patch should go thru Richard's led-2.6.git as it depends on another
one that has been queued there already.
Thanks,
Daniel
>From fd5915cf86c659eac67a8c0ea4379a78efbe2231 Mon Sep 17 00:00:00 2001
From: Daniel Mack <daniel@caiaq.de>
Date: Tue, 13 Oct 2009 12:42:52 +0800
Subject: [PATCH] leds-alix2: add support for button connected to J15
The ALIX2 boards have one GPIO pin which is reachable at connector J15.
One possible application for this feature is to connect a button which
closes the two pins.
This patch adds support to query these button and export its state via
an input device.
Signed-off-by: Daniel Mack <daniel@caiaq.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>
Cc: linux-input@vger.kernel.org
Cc: Constantin Baranov <const@mimas.ru>
---
drivers/leds/Kconfig | 14 ++++++++++++
drivers/leds/leds-alix2.c | 50 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 64 insertions(+), 0 deletions(-)
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index e4f599f..7e57bba 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -77,6 +77,20 @@ config LEDS_ALIX2
This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
You have to set leds-alix2.force=1 for boards with Award BIOS.
+config LEDS_ALIX2_BUTTON
+ bool "Input device support for button on ALIX boards"
+ depends on LEDS_ALIX2 && INPUT
+ select INPUT_POLLDEV
+ help
+ This option enables support for a button connected to J15 of ALIX
+ boards.
+
+ Note that for this feature to work, there is need for a minor
+ modification to the hardware. R1 needs to be removed, and R4 needs
+ to be places as 100KOhms pull-up.
+
+ Only select that option if you modified your ALIX board like this.
+
config LEDS_H1940
tristate "LED Support for iPAQ H1940 device"
depends on LEDS_CLASS && ARCH_H1940
diff --git a/drivers/leds/leds-alix2.c b/drivers/leds/leds-alix2.c
index f59ffad..e41b252 100644
--- a/drivers/leds/leds-alix2.c
+++ b/drivers/leds/leds-alix2.c
@@ -12,6 +12,7 @@
#include <linux/platform_device.h>
#include <linux/string.h>
#include <linux/pci.h>
+#include <linux/input-polldev.h>
static int force = 0;
module_param(force, bool, 0444);
@@ -29,6 +30,12 @@ static struct pci_device_id divil_pci[] = {
};
MODULE_DEVICE_TABLE(pci, divil_pci);
+#ifdef CONFIG_LEDS_ALIX2_BUTTON
+static struct input_polled_dev *ipdev;
+static int alix_button_last;
+#define POLL_INTERVAL_DEFAULT 250
+#endif
+
struct alix_led {
struct led_classdev cdev;
unsigned short port;
@@ -78,6 +85,20 @@ static struct alix_led alix_leds[] = {
},
};
+#ifdef CONFIG_LEDS_ALIX2_BUTTON
+static void alix_button_poll(struct input_polled_dev *ipdev)
+{
+ unsigned int val = !(inl(gpio_base + 0x30) & (1 << 1));
+
+ if (val == alix_button_last)
+ return;
+
+ input_report_key(ipdev->input, BTN_MISC, val);
+ input_sync(ipdev->input);
+ alix_button_last = val;
+}
+#endif
+
static int __init alix_led_probe(struct platform_device *pdev)
{
int i;
@@ -89,6 +110,35 @@ static int __init alix_led_probe(struct platform_device *pdev)
if (ret < 0)
goto fail;
}
+
+#ifdef CONFIG_LEDS_ALIX2_BUTTON
+ /* enable button input */
+ outl(1 << 1, gpio_base + 0x20);
+
+ /* enable pullup on input pin */
+ outl(1 << 1, gpio_base + 0x18);
+
+ alix_button_last = 0;
+ ipdev = input_allocate_polled_device();
+ if (!ipdev)
+ goto fail;
+
+ ipdev->poll = alix_button_poll;
+ ipdev->poll_interval = POLL_INTERVAL_DEFAULT;
+ ipdev->input->name = "ALIX2 button";
+ ipdev->input->phys = "alix2/input0";
+ ipdev->input->id.bustype = BUS_HOST;
+
+ set_bit(EV_KEY, ipdev->input->evbit);
+ ipdev->input->keybit[BIT_WORD(BTN_MISC)] = BIT_MASK(BTN_MISC);
+
+ ret = input_register_polled_device(ipdev);
+ if (ret) {
+ input_free_polled_device(ipdev);
+ goto fail;
+ }
+#endif
+
return 0;
fail:
--
1.6.0.4
next reply other threads:[~2009-10-16 13:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 13:03 Daniel Mack [this message]
2009-10-18 7:27 ` [PATCH] leds-alix2: add support for button connected to J15 Dmitry Torokhov
2009-10-19 7:37 ` Daniel Mack
2009-10-20 1:38 ` Dmitry Torokhov
2009-10-20 10:13 ` Daniel Mack
2009-10-21 4:35 ` Dmitry Torokhov
2009-10-21 19:33 ` Daniel Mack
2009-10-21 20:21 ` Constantin Baranov
2009-10-21 20:41 ` Daniel Mack
2009-10-21 21:39 ` Constantin Baranov
2009-10-21 22:09 ` Constantin Baranov
2009-10-22 10:11 ` Daniel Mack
2009-10-18 10:56 ` Richard Purdie
2009-10-19 7:16 ` Daniel Mack
2009-10-22 10:29 ` Pavel Machek
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=20091016130315.GT28832@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=const@mimas.ru \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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).