From: Jiri Kosina <jikos@jikos.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: detecting when keys are being pressed on a keyboard
Date: Mon, 24 Sep 2007 15:45:59 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709241544540.22331@twin.jikos.cz> (raw)
In-Reply-To: <200709241256.05300.oliver@neukum.org>
On Mon, 24 Sep 2007, Oliver Neukum wrote:
> > HID doesn't keep any permanent state by itself. If you want to know
> > whether a given key is currently pressed or not, you'd have to inspect
> > the bitfields inside input_dev*, I am afraid.
> I see no way to do this without a race condition. The field isn't locked
> as far as I can tell.
Hi Oliver,
Dmitry (CC added) has been doing a lot of rework of locking in input as
far as I know. He would know this better.
> Secondly, what is to happen in case of a system wide suspend? Will
> the system wake up thinking that the key is still pressed?
If the release event didn't happen before the machine went to suspend, I'd
say so.
--
Jiri Kosina
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
prev parent reply other threads:[~2007-09-24 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 8:33 detecting when keys are being pressed on a keyboard Oliver Neukum
2007-09-21 12:47 ` Jiri Kosina
2007-09-24 10:56 ` Oliver Neukum
2007-09-24 12:50 ` [linux-usb-devel] " Dmitry Torokhov
2007-09-24 13:39 ` Oliver Neukum
2007-09-24 13:45 ` Dmitry Torokhov
2007-09-24 13:54 ` Oliver Neukum
2007-09-24 13:45 ` Jiri Kosina [this message]
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=Pine.LNX.4.64.0709241544540.22331@twin.jikos.cz \
--to=jikos@jikos.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.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).