Thread (6 messages) 6 messages, 2 authors, 2010-02-05

Re: [RFC] Generic implementation for Input enable disable methods

From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2010-02-05 08:11:00

On Thursday 04 February 2010 11:38:41 pm samu.p.onkalo@nokia.com wrote:
quoted
-----Original Message-----
From: ext Dmitry Torokhov [mailto:dmitry.torokhov@gmail.com]

Hi Samu,

I still believe that the only thing we need (apart of special plumbing
in
gpio-keys) is a way for userspace clients to subsribe on unsubscribe
from certain events rather than device-wide configuration. This way we
can avoid waking up processes that are not interested in some of the
events.
Hi Dmitry,

I just noticed that control interface for gpio was applied to input-tree.
We still have a need to disable hw in certain cases. It is probably better
to forget generic implementation to input core and make control interface
as specific to each driver like proposed some months ago for example
for tel4030-keypad driver. Or what do you think?

Sw filtering which avoids to wakeup some processes is not proper solution
to embedded devices. We need to avoid waking up the processor itself.
I see. I think that such facility should not be limited to input devices
(with the exception of gpio-keys which is a special case since it works
with multiple interrupts). We need a way to allow userspace initiate
putting an arbitrary device to "sleep" and this should be generic
infrastructure.

So you need to talk to PM people again and design such facility with them
since IIRC there wasn't anything like that last time you tried asking that
question.

Thanks.

-- 
Dmitry
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help