From: Oliver Neukum <oliver@neukum.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jiri Kosina <jkosina@suse.cz>,
USB list <linux-usb@vger.kernel.org>,
linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [patch]full autosuspend for USB HID
Date: Wed, 7 May 2008 19:13:35 +0200 [thread overview]
Message-ID: <200805071913.36445.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0805071145130.3701-100000@iolanthe.rowland.org>
Am Mittwoch 07 Mai 2008 17:46:38 schrieb Alan Stern:
> > The basic strategy for input is to keep the device marked busy. The bulk of the
> > patch is for output, the work around for the release stuff and synchronization.
>
> One big problem we always faced with autosuspend for keyboards is that
> most of them were not able to autoresume quickly enough to avoid losing
> keystrokes. Isn't that still a problem?
For some keyboards that seems to be a limitation of the hardware nothing
can be done about. Others do work, for example 046d:c312. Generally
as autosuspend is now disabled by default this is user space's problem.
IMHO the main use case for autosuspend of keyboards will be synchronized
with the screen saver.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-05-07 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 12:50 [patch]full autosuspend for USB HID Oliver Neukum
[not found] ` <200805071450.39499.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2008-05-07 15:46 ` Alan Stern
2008-05-07 15:49 ` Jiri Kosina
2008-05-07 15:57 ` Alan Stern
2008-05-07 15:59 ` Jiri Kosina
[not found] ` <Pine.LNX.4.64.0805071758240.11363-YCXOAqNspd+N3ZZ/Hiejyg@public.gmane.org>
2008-05-07 16:06 ` Alan Stern
2008-05-07 17:18 ` Oliver Neukum
2008-05-07 17:13 ` Oliver Neukum [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=200805071913.36445.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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