From: Constantin Baranov <const@mimas.ru>
To: Daniel Mack <daniel@caiaq.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] leds-alix2: add support for button connected to J15
Date: Thu, 22 Oct 2009 01:21:21 +0500 [thread overview]
Message-ID: <20091022012121.5b35ff22.const@mimas.ru> (raw)
In-Reply-To: <20091021193347.GL14091@buzzloop.caiaq.de>
Hi, Daniel!
I wonder why do you integrate the input driver into the leds driver. They
should be separated. Or at least the complex driver should be moved to the
"X86 Platform Specific Device Drivers" and renamed to some like "PC Engines
ALIX Extras". I personally would prefer the separation way.
Also ALIX.2 documentation describes the "Mode switch" driven by GPIO which is a
small button on front side of a board. I guessed your driver is not for this
button. If so, would it be better to provide the mode switch as KEY_PROG1 and
the J15 connected button as KEY_PROG2 at once?
Cheers,
Constantin
> From 66953e5dda7bbbc22b92541ed3a6020773c62140 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>
next prev parent reply other threads:[~2009-10-21 20:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 13:03 [PATCH] leds-alix2: add support for button connected to J15 Daniel Mack
2009-10-18 7:27 ` 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 [this message]
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=20091022012121.5b35ff22.const@mimas.ru \
--to=const@mimas.ru \
--cc=daniel@caiaq.de \
--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).