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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 2 Oct 2013 11:57:23 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Daniel Mack <zonque@...il.com>
Cc:	Fabio Estevam <festevam@...il.com>, linux-gpio@...r.kernel.org,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] drivers: misc: add gpio wakeup driver

On Tue, Oct 01, 2013 at 04:05:07PM +0200, Daniel Mack wrote:
> On 01.10.2013 16:01, Fabio Estevam wrote:

> > Isn't it the same as the existing 'gpio-key,wakeup' ?

> Of course, I know the gpio-input driver can provide similar
> functionality. My intention was just provide a way to wake up the system
> without registering an input device for signals nobody is interested in
> eventually.

> Don't know if that's reason enough to add a new driver though.

It does seem somewhat sensible - the signal might not have a sensible
representation as an input device and the gpio-keys binding needs one.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ