linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Onkalo Samu <samu.p.onkalo@nokia.com>
To: ext Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: [RFC] Generic implementation for Input enable disable methods
Date: Wed, 20 Jan 2010 08:28:40 +0200	[thread overview]
Message-ID: <1263968920.18053.24.camel@4fid08082> (raw)


Hi

Some time ago, there were two parallel implementation proposals for
disabling input devices. See following email:
http://www.spinics.net/lists/linux-input/msg05984.html

It was asked to combine these two to have generic interface.
I'm proposing following sysfs interface:

../input0/disable/avail_xx
../input0/disable/disable_xx

So, new directory for disable control entries. Own entries for each
of the events or event group. Implementation is using bitmap format:

Examples

See what event groups can be disabled. Disable and enable all the groups
# cat avail_ev
0-1,4,20
# echo "0-1,4,20" > disable_ev
# cat disable_ev
0-1,4,20
# echo -e "\0" > disable_ev
# cat disable_ev
 
See what individual events can be disabled. Disable and enable one of
them:
# cat avail_key
528
# echo "528" > disable_key
# cat disable_key
528
# echo -e "\0" -> disable_key
# cat disable_key

Input core just provides sysfs entries and call call-back functions. 
Actual work is done in the drivers like gpio-keys.

Does this interface sound acceptable solution?
If it is, I'll finalize my implentation and send it for review.
This interface is tested to work with twl4030_keypad driver and
gpio-keys. It should also work fine with touch screen input drivers.

This is more or less small embedded device feature. Should it be behind
configuration flags similar to CONFIG_PM? Of course this would introduce
some compilation flags to the input-core.

Regard,
Samu




             reply	other threads:[~2010-01-20  6:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20  6:28 Onkalo Samu [this message]
2010-01-22  6:28 ` [RFC] Generic implementation for Input enable disable methods Onkalo Samu
2010-02-01  8:59   ` Dmitry Torokhov
2010-02-05  7:38     ` samu.p.onkalo
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=1263968920.18053.24.camel@4fid08082 \
    --to=samu.p.onkalo@nokia.com \
    --cc=dmitry.torokhov@gmail.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).