linux-kernel - Re: [PATCH] gpio: export 'debounce' attribute if supported by the gpio chip

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121209110319.459a762a@pyramind.ukuu.org.uk>
Date:	Sun, 9 Dec 2012 11:03:19 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	anish kumar <anish198519851985@...il.com>
Cc:	Guenter Roeck <groeck-dsl@...global.net>,
	Linus Walleij <linus.walleij@...aro.org>,
	Guenter Roeck <linux@...ck-us.net>,
	linux-kernel@...r.kernel.org,
	Grant Likely <grant.likely@...retlab.ca>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [PATCH] gpio: export 'debounce' attribute if supported by the
 gpio chip

On Sun, 09 Dec 2012 01:58:19 -0800
anish kumar <anish198519851985@...il.com> wrote:

> On Fri, 2012-12-07 at 16:49 +0000, Alan Cox wrote:
> > > I could imagine declaring the activity request buttons to be "input", but for
> > > presence detects it is a bit far fetched and would add too much complexity.
> > 
> > Android tries to address this with its switch class driver, but I'm not
> > sure its actually got anything over making them input devices.
> 
> Sorry for not understanding the context here.How the debounce sysfs
> added by Guenter has anything to do with switch driver in android?

The other more general option is to make the input layer do the debounce
and make them all inputs rather than just relying on any gpio layer
support.


--
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/