From: pHilipp Zabel <philipp.zabel@gmail.com>
To: Jani Nikula <ext-jani.1.nikula@nokia.com>
Cc: david-b@pacbell.net, linux-kernel@vger.kernel.org,
juha.yrjola@solidboot.com
Subject: Re: [RFC PATCH 0/3] GPIO switch framework
Date: Fri, 20 Mar 2009 15:15:59 +0100 [thread overview]
Message-ID: <74d0deb30903200715v7de33289mcbd49cb44f629b46@mail.gmail.com> (raw)
In-Reply-To: <1237557050-13742-1-git-send-email-ext-jani.1.nikula@nokia.com>
Hi,
On Fri, Mar 20, 2009 at 2:50 PM, Jani Nikula
<ext-jani.1.nikula@nokia.com> wrote:
>
> Hi -
>
> This RFC patchset is a pretty straightforward adaptation of OMAP GPIO
> switch framework for mainline integration.
>
> The GPIO switch framework allows reporting and changing GPIO switches
> via sysfs, with debouncing and sysfs/in-kernel notifications for input
> switches.
Doesn't this partially duplicate what the input layer is for?
There is also a gpio-keys driver in input/keyboard already that can
report switch events (EV_SW) to the input layer, but it doesn't have
the in-kernel notification.
> The switches are added as /sys/class/gpio/switch-<switch name> under
> the gpiolib sysfs structure.
>
> BR,
> Jani.
>
>
> Jani Nikula (3):
> GPIOLIB: Add new gpio_device_create function
> GPIO-SWITCH: Adaptation of GPIO switch framework for mainline
> GPIO-SWITCH: Kconfig and Makefile
>
> drivers/gpio/Kconfig | 10 +
> drivers/gpio/Makefile | 2 +
> drivers/gpio/gpio-switch.c | 534 +++++++++++++++++++++++++++++++++++++++++++
> drivers/gpio/gpiolib.c | 52 +++++
> include/asm-generic/gpio.h | 12 +
> include/linux/gpio-switch.h | 74 ++++++
> 6 files changed, 684 insertions(+), 0 deletions(-)
> create mode 100644 drivers/gpio/gpio-switch.c
> create mode 100644 include/linux/gpio-switch.h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
regards
Philipp
next prev parent reply other threads:[~2009-03-20 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 13:50 Jani Nikula
2009-03-20 13:50 ` [RFC PATCH 1/3] GPIOLIB: Add new gpio_device_create function Jani Nikula
2009-03-20 13:50 ` [RFC PATCH 2/3] GPIO-SWITCH: Adaptation of GPIO switch framework for mainline Jani Nikula
2009-03-20 13:50 ` [RFC PATCH 3/3] GPIO-SWITCH: Kconfig and Makefile Jani Nikula
2009-03-20 14:15 ` pHilipp Zabel [this message]
2009-03-22 6:25 ` [RFC PATCH 0/3] GPIO switch framework Ben Nizette
2009-03-31 9:18 ` Jani Nikula
2009-07-01 21:03 ` David Brownell
2009-07-02 9:07 ` Jani Nikula
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=74d0deb30903200715v7de33289mcbd49cb44f629b46@mail.gmail.com \
--to=philipp.zabel@gmail.com \
--cc=david-b@pacbell.net \
--cc=ext-jani.1.nikula@nokia.com \
--cc=juha.yrjola@solidboot.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®