lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 22 Mar 2009 17:25:21 +1100 From: Ben Nizette <bn@...sdigital.com> To: Jani Nikula <ext-jani.1.nikula@...ia.com> Cc: david-b@...bell.net, linux-kernel@...r.kernel.org, juha.yrjola@...idboot.com Subject: Re: [RFC PATCH 0/3] GPIO switch framework 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists