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 17:54:39 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.0905011751180.5012@wotan.suse.de> (raw)
In-Reply-To: <200905011102.18945.oliver@neukum.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 928 bytes --]

On Fri, 1 May 2009, Oliver Neukum wrote:

> > > > +       if (!(hid->claimed & HID_CLAIMED_INPUT))
> > > > +               return 0;
> > > > +
> > > is there a guarantee all keyboards will be claimed as input devices?
> > do you see any way how hid->inputs could currently be initialized other
> > than the device being claimed by hid-input?
> No, but I am worried about a false return of 0 here, not the other way
> round. This method is necessary because keyboards don't wake up
> if a key is released. Suspending a keyboard with a key pressed will lead
> to an endless repetition of that key.
> So I wonder whether it is possible to have a keyboard not claimed as an
> input device.

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?

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2009-05-01 15:54 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 [this message]
2009-05-01 16:09             ` Oliver Neukum
2009-05-01 16:16               ` Jiri Kosina
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.0905011751180.5012@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®