From: Trilok Soni <soni.trilok@gmail.com>
To: linux-input@vger.kernel.org
Subject: Handling stuck keys
Date: Mon, 7 Sep 2009 16:32:06 +0530 [thread overview]
Message-ID: <5d5443650909070402s33ec5385h49df18821507ea5d@mail.gmail.com> (raw)
Hi,
What is the preferred way to handle stuck key notification through driver?
I feel the following scenario would work assuming that controller is
able to detect the stuck key and gives us an interrupt.
- Once the interrupt is raised, we go and find out which key is stuck
through regular key scanning logic.
- We find the key which is the vicitim and forcefully send "release"
key event through input_report_key.
I saw other drivers in the input subsystem where people are handling
keyboard quirks with forceful release, so I hope the same should with
stuck keys too.
--
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni
next reply other threads:[~2009-09-07 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 11:02 Trilok Soni [this message]
2009-09-08 6:29 ` Handling stuck keys Dmitry Torokhov
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=5d5443650909070402s33ec5385h49df18821507ea5d@mail.gmail.com \
--to=soni.trilok@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).