From: Herbert Valerio Riedel <hvr@gnu.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, Paul Sokolovsky <pmiscml@gmail.com>,
Philipp Zabel <philipp.zabel@gmail.com>,
Philip Blundell <philb@gnu.org>
Subject: Re: [PATCH,RFC] Input: gpio-keys - request and configure GPIOs
Date: Fri, 16 Nov 2007 15:09:11 +0100 [thread overview]
Message-ID: <1195222151.10848.47.camel@pbook.intra> (raw)
In-Reply-To: <d120d5000711160538u6f629e34h9465a880f09be49c@mail.gmail.com>
On Fri, 2007-11-16 at 08:38 -0500, Dmitry Torokhov wrote:
> On Nov 16, 2007 6:33 AM, Herbert Valerio Riedel <hvr@gnu.org> wrote:
> > Currently, gpio_keys.c assumes the GPIOs to be already properly configured;
> > this patch changes gpio-keys to perform explicit calls to gpio_request() and
> > gpio_configure_input().
> >
> > This matches the behaviour of leds-gpio.
> Makes sense from where I sit but let's see what guys who actually use
> the module say... ;)
I grepped through my 2.6.24-git source tre, and the only places I found
gpio_keys.h included was
drivers/input/keyboard/gpio_keys.c:#include <linux/gpio_keys.h>
arch/arm/mach-orion/dns323-setup.c:#include <linux/gpio_keys.h>
arch/arm/mach-at91/board-sam9261ek.c:#include <linux/gpio_keys.h>
with dn323-setup.c being maintained by myself, and board-sam9261ek.c
having seemingly non-compilable code wrt to gpio_keys (for instance, it
uses ".keycode" gpio_keys_button struct members which should have been
".code"), there don't seem to exist many users of that module...? :-)
cheers,
hvr
next prev parent reply other threads:[~2007-11-16 15:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 11:33 [PATCH,RFC] Input: gpio-keys - request and configure GPIOs Herbert Valerio Riedel
2007-11-16 11:50 ` Herbert Valerio Riedel
2007-11-16 13:38 ` Dmitry Torokhov
2007-11-16 14:02 ` pHilipp Zabel
2007-11-16 14:15 ` Herbert Valerio Riedel
2007-11-16 14:09 ` Herbert Valerio Riedel [this message]
2007-11-16 14:19 ` pHilipp Zabel
2007-11-21 17:13 ` Herbert Valerio Riedel
2007-11-21 19:44 ` Dmitry Torokhov
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=1195222151.10848.47.camel@pbook.intra \
--to=hvr@gnu.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=philb@gnu.org \
--cc=philipp.zabel@gmail.com \
--cc=pmiscml@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.