On 02.10.2013 12:57, Mark Brown wrote: > 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. > That was my intention as well, yes. Also, a system that does not have any input devices could in theory disable CONFIG_INPUT alltogether. Not sure how realisitic that scenario really is nowadays, but using the gpio input driver for purpose of just waking up on LAN seems somewhat abusive. Daniel -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
