mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: Guillaume Chazarain <guichaz@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: What's in hid.git for 2.6.30
Date: Fri, 1 May 2009 18:16:11 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.0905011812330.22532@wotan.suse.de> (raw)
In-Reply-To: <200905011809.19971.oliver@neukum.org>

On Fri, 1 May 2009, Oliver Neukum wrote:

> > If driven by usbhid, the only way how keyboard could be handled if not
> > claimed by hid-input is a userspace hiddev or hidraw driver. And we don't
> > suspend if hidraw/hiddev node is open, right?
> What happens if the node is closed? 

That's up to the userspace driver. If it is an input driver, it is 
probably using uinput to inject events into the input system, and 
therefore should properly unregister itself also from uinput together with 
closing the node.

> Will hid forget that a key had been pressed? I must admit that I can't 
> tell where in hid the key repetition logic is located.

The repetition is fully handled in the input core, not in the hid-input 
driver. So if the device is not handled by hid-input, we (the kernel 
driver) haven't registered with the input subsystem, and therefore no 
events go to input subsystem at all.

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2009-05-01 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 23:07 Jiri Kosina
2009-04-30 22:29 ` Guillaume Chazarain
2009-04-30 22:45   ` Jiri Kosina
2009-04-30 23:02     ` Oliver Neukum
2009-04-30 23:09       ` Jiri Kosina
2009-05-01  9:02         ` Oliver Neukum
2009-05-01 15:54           ` Jiri Kosina
2009-05-01 16:09             ` Oliver Neukum
2009-05-01 16:16               ` Jiri Kosina [this message]
2009-05-01 16:49                 ` Oliver Neukum
2009-04-30 23:37     ` Guillaume Chazarain

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=alpine.LNX.2.00.0905011812330.22532@wotan.suse.de \
    --to=jkosina@suse.cz \
    --cc=guichaz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®