linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-usb-devel@lists.sourceforge.net,
	linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [linux-usb-devel] detecting when keys are being pressed on a keyboard
Date: Mon, 24 Sep 2007 15:39:19 +0200	[thread overview]
Message-ID: <200709241539.19610.oliver@neukum.org> (raw)
In-Reply-To: <d120d5000709240550u3bb1d455vc9bb54b2e57f4313@mail.gmail.com>

Am Montag 24 September 2007 schrieb Dmitry Torokhov:
> Hi Oliver,
> 
> On 9/24/07, Oliver Neukum <oliver@neukum.org> wrote:
> > Am Freitag 21 September 2007 schrieb Jiri Kosina:

> > > Hi Oliver,
> > >
> > > 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.
> 
> You can take input_dev->event_lock to stop event from propagating
> through input core while you are evaluating the bits. Input lcoking
> changes are im -mm and will be merged into 2.6.24.

Hi Dmitry,

I was thinking about a second approach. As all keypresses run through
the interrupt handlers of the hid driver, how about checking the bit field
in the interrupt handler after calling hid_input_report() ?

	Regards
		Oliver

  reply	other threads:[~2007-09-24 13:39 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 [this message]
2007-09-24 13:45         ` Dmitry Torokhov
2007-09-24 13:54           ` Oliver Neukum
2007-09-24 13:45     ` Jiri Kosina

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=200709241539.19610.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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).