Hi! > > Yeah, that would be nice. But it won't work for us :( > > > > This is because the actual input device might be open for several > > applications. Then we have single process which controls state of > > the device. Now if, for example the device is locked by user, this > > process just disables those buttons which are not allowed to wake > > up the device and blanks the screen. > > > > So the input device is still open but we just prevent GPIO lines > > from generating any interrupts while the device is locked. There > > are other use-cases also where different buttons are > > disabled/enabled. > > Hi, > > I thought we'd better ask our friends over at linux-pm, if they've got > some interface for this task. To summarize: an embedded application > wants to go into a "locked" state, where some input devices (gpio keys > in this case) are "muted", ie. they don't even generate interrupts to > minimize power consumption. This could be solved by adding a new > interface to gpio-keys, but the problem seems more general, so I wonder Is it so bright idea? How much power does it save? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
