From: Oliver Neukum <oliver@neukum.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>,
"linux-input" <linux-input@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] [PATCH] Input: add appleir USB driver
Date: Tue, 5 Oct 2010 08:02:14 +0200 [thread overview]
Message-ID: <201010050802.14271.oliver@neukum.org> (raw)
In-Reply-To: <20101005044520.GA14707@core.coreip.homeip.net>
Am Dienstag, 5. Oktober 2010, 06:45:20 schrieb Dmitry Torokhov:
> > > +{
> > > + struct appleir *appleir = input_get_drvdata(dev);
> > > +
> > > + mutex_lock(&appleir_mutex);
> > > +
> > > + if (!(appleir->flags & APPLEIR_SUSPENDED)) {
> > > + usb_kill_urb(appleir->urb);
> > > + del_timer_sync(&appleir->key_up_timer);
> >
> > You can close with a key unreleased.
>
> I think this is handled by input core. We forcibly send release events
> when device is disconnected; this takes care of surprise disconnect case.
> OTOH if input_dev->close() is called that means that there are no more
> listeners for the events so the fact that a key is still pressed is not
> interesting to anyone.
But what about the next opener? He'll get a completely spurious
key release event, as the next key is pressed.
> > > + usb_kill_urb(appleir->urb);
> >
> > If the system goes to sleep you'd better report a pressed key
> > as released here and kill the timer.
>
> Input core sends "release" events upon resume so we should be OK.
I see. OK, this is covered.
Regards
Oliver
next prev parent reply other threads:[~2010-10-05 6:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 10:57 Bastien Nocera
2010-09-30 15:47 ` Dmitry Torokhov
2010-09-30 15:51 ` Bastien Nocera
2010-10-08 0:39 ` Jarod Wilson
2010-11-18 4:18 ` Bastien Nocera
2010-11-19 18:07 ` Jarod Wilson
2010-10-04 19:17 ` Oliver Neukum
2010-10-05 4:45 ` Dmitry Torokhov
2010-10-05 6:02 ` Oliver Neukum [this message]
2010-10-05 6:08 ` Dmitry Torokhov
2010-10-05 6:18 ` Oliver Neukum
2010-10-05 15:55 ` Dmitry Torokhov
2010-10-05 16:07 ` Oliver Neukum
2010-10-05 16:18 ` 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=201010050802.14271.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome