From: <samu.p.onkalo@nokia.com>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, ext-mika.1.westerberg@nokia.com,
ext-jani.1.nikula@nokia.com
Subject: RE: [RFC] Generic implementation for Input enable disable methods
Date: Fri, 5 Feb 2010 08:38:41 +0100 [thread overview]
Message-ID: <62697B07E9803846BC582181BD6FB6B8257283DAC4@NOK-EUMSG-02.mgdnok.nokia.com> (raw)
In-Reply-To: <20100201085901.GC24188@core.coreip.homeip.net>
>-----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.
Br,
Samu
next prev parent reply other threads:[~2010-02-05 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 6:28 [RFC] Generic implementation for Input enable disable methods Onkalo Samu
2010-01-22 6:28 ` Onkalo Samu
2010-02-01 8:59 ` Dmitry Torokhov
2010-02-05 7:38 ` samu.p.onkalo [this message]
2010-02-05 8:10 ` Dmitry Torokhov
2010-02-05 8:46 ` samu.p.onkalo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62697B07E9803846BC582181BD6FB6B8257283DAC4@NOK-EUMSG-02.mgdnok.nokia.com \
--to=samu.p.onkalo@nokia.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ext-jani.1.nikula@nokia.com \
--cc=ext-mika.1.westerberg@nokia.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).