Am Mittwoch 07 Mai 2008 17:46:38 schrieb Alan Stern:

quoted

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