From: Oliver Neukum <oneukum@suse.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Tom Gundersen <teg@jklm.no>,
linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] usbhid: enable autosuspend for internal devices
Date: Mon, 29 Jun 2015 11:48:12 +0200 [thread overview]
Message-ID: <1435571292.1805.4.camel@suse.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1506270825010.10183@pobox.suse.cz>
On Sat, 2015-06-27 at 08:29 +0200, Jiri Kosina wrote:
> On Fri, 26 Jun 2015, Greg Kroah-Hartman wrote:
> Last time we were testing this, autosuspend for USB HID devices was quite
> a disaster.
>
> Do you have any idea whether udev developers tested the "autosuspend on by
> default for USB HID devices" on reasonable set of devices?
>
> The culrpits that I remember from top of my head (it's been long time
> ago):
>
> - the LEDs for suspended device go off. This is very confusing at least on
> keyboards, and brings really bad user experience
That is a bug. hidinput_count_leds() is supposed to prevent that.
What did you test?
> - many keyboards were losing first keystroke when waking up from suspend.
> We've been debugging this with Alan, and never root-caused it to a
> problem in our code, it seems to be the property of the HW
- mice don't wake up from movement alone.
And again I would state that we don't get enough information
from user space. Hardware seems to be designed for sleeping
while a screen saver is on. In kernel space we just get a binary
input desired or not desired from open/close.
That is insufficient.
Regards
Oliver
next prev parent reply other threads:[~2015-06-29 9:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 19:24 [PATCH][RFC] usbhid: enable autosuspend for internal devices Tom Gundersen
2015-06-26 19:32 ` Greg Kroah-Hartman
2015-06-26 20:08 ` Alan Stern
2015-06-26 20:08 ` Alan Stern
2015-06-26 20:28 ` Alan Stern
2015-06-26 20:28 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1506261549310.1566-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2015-06-26 22:15 ` Greg Kroah-Hartman
2015-06-26 22:15 ` Greg Kroah-Hartman
[not found] ` <20150626221517.GB2761-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-06-27 1:20 ` Alan Stern
2015-06-27 1:20 ` Alan Stern
2015-06-27 1:29 ` Greg Kroah-Hartman
2015-06-27 6:29 ` Jiri Kosina
[not found] ` <alpine.LNX.2.00.1506270825010.10183-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2015-06-27 15:31 ` Greg Kroah-Hartman
2015-06-27 15:31 ` Greg Kroah-Hartman
2015-06-30 15:21 ` Alan Stern
2015-06-30 15:21 ` Alan Stern
2015-06-29 9:48 ` Oliver Neukum [this message]
2015-06-29 11:16 ` Jiri Kosina
2015-06-29 11:37 ` Oliver Neukum
[not found] ` <1435577839.1805.10.camel-l3A5Bk7waGM@public.gmane.org>
2015-06-29 12:00 ` Jiri Kosina
2015-06-29 12:00 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2015-07-02 7:18 Andreas Mohr
2015-07-02 14:08 ` Alan Stern
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=1435571292.1805.4.camel@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=teg@jklm.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.