From: Ben Nizette <bn@niasdigital.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: Sun, 22 Mar 2009 17:25:21 +1100 [thread overview]
Message-ID: <1237703121.2720.39.camel@linux-51e8.site> (raw)
In-Reply-To: <1237557050-13742-1-git-send-email-ext-jani.1.nikula@nokia.com>
On Fri, 2009-03-20 at 15:50 +0200, Jani Nikula 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.
OK, so what does this do that /sys/class/gpio/gpioN doesn't currently do
apart from debouncing? And the output being a string rather than a
simple value (which IMO might be better suited to userspace
interpretation anyway).
I've got a patch, little abandoned at the bottom of my queue, which adds
poll(2) compatibility to the gpiolib sysfs entries [1] and extending
this patch to do debouncing as well would be almost trivial.
I guess what I'm getting at is that this seems like it solves a problem
which has been pretty much solved elsewhere since the OMAP boys wrote
this.
--Ben.
[1] http://marc.info/?l=linux-kernel&m=122454305213792&w=2
next prev parent reply other threads:[~2009-03-22 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 13:50 [RFC PATCH 0/3] GPIO switch framework 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 ` [RFC PATCH 0/3] GPIO switch framework pHilipp Zabel
2009-03-22 6:25 ` Ben Nizette [this message]
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=1237703121.2720.39.camel@linux-51e8.site \
--to=bn@niasdigital.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