| 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: Thu, 11 Nov 2010 14:15:46 +0000 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: "Lighthart, EricX" <ericx.lighthart@...el.com> Cc: "dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>, "pb@...dhelds.org" <pb@...dhelds.org>, "ext-mika.1.westerberg@...ia.com" <ext-mika.1.westerberg@...ia.com>, "linux-input@...r.kernel.org" <linux-input@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] input: Add sysfs interface to on/off state of GPIO keys and switches On Thu, Nov 11, 2010 at 06:03:35AM -0800, Lighthart, EricX wrote: > User space cannot learn the current state of a GPIO key or switch. > Input system reports only changes, not state. > > Add two sysfs attributes, one each for keys and switches, that > report lists of keys or switches currently "on." There's EVIOCG* ioctl()s for this. Something sysfs (or a widely distributed utility) would be very helpful but there is actually a facility to read the state. > drivers/input/keyboard/gpio_keys.c | 68 ++++++++++++++++++++++++++++-------- If something is needed here it should be done as part of the input layer, not in a driver specific fashion - there's nothing specific to GPIO keys here. -- 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