Linux Hotplug development
 help / color / mirror / Atom feed
From: Roland Ramthun <mail@roland-ramthun.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: USB suspend and Logitech Iilluminated Keyboard
Date: Mon, 01 Nov 2010 16:38:29 +0000	[thread overview]
Message-ID: <20101101173829.356a1ca6.mail@roland-ramthun.de> (raw)
In-Reply-To: <20101031183827.31d721ef.mail@roland-ramthun.de>

On Mon, 1 Nov 2010 16:33:38 +0100
Kay Sievers <kay.sievers@vrfy.org> wrote:

> > I wrote an udev rule to disable USB suspend for this specific model, which solves the described problems. You'll find it attached.
> >
> > Is there another way to circumvent this problem?
> 
> I think usb-auto-suspend is usually off by default and needs to be
> enabled per device. The idea is/was to have whitelist of devices and
> enable devices which are known to be safe. But as far as I know, no
> such list exists or is in common use.

You mean the device driver needs to enable it?
The Logitech is a standard USB keyboard.

[3.052761] generic-usb 0003:046D:C318.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech Illuminated Keyboard] on usb-0000:00:1d.0-1.1/input0
[3.279286] generic-usb 0003:046D:C318.0002: input,hiddev96,hidraw1: USB HID v1.11 Device [Logitech Logitech Illuminated Keyboard] on usb-0000:00:1d.0-1.1/input1

I think this suggests it uses "normal" USB HID drivers.

Reading the USB power management documentation it turns out, such problems are known.

Documentation/usb/power-management.txt
==
Sometimes it turns out that even when a device does work okay with
autosuspend there are still problems.  For example, there are
experimental patches adding autosuspend support to the usbhid driver,
which manages keyboards and mice, among other things.  Tests with a
number of keyboards showed that typing on a suspended keyboard, while
causing the keyboard to do a remote wakeup all right, would
nonetheless frequently result in lost keystrokes.
==

I'm sure I have no "experimental patches" applied, I use a vanilla 2.6.34 kernel.

> > If not, please consider to include this rule into the official udev release.
> 
> Besides a few (pretty broken) exceptions the udev sources do not carry
> quirks for individual devices, only generic subsystem specific things.

I see how that's reasonable, as this list would need constant care and could become large.
E.g. in the meantime I discovered the same problems exist with a Logitech G15, too.

> We can't add this at the moment, there is at the moment no
> infrastructure to keep lists like this maintained.

Obviously we shouldn't add these exceptions to udev.
But what is the right place?
Judging from the above documentation snippet, there might be something wrong with the fact USB suspend is active on a keyboard at all.

Kind regards,
Roland

  parent reply	other threads:[~2010-11-01 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 17:38 USB suspend and Logitech Iilluminated Keyboard Roland Ramthun
2010-11-01 15:33 ` Kay Sievers
2010-11-01 16:38 ` Roland Ramthun [this message]
2010-11-01 16:46 ` Kay Sievers

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=20101101173829.356a1ca6.mail@roland-ramthun.de \
    --to=mail@roland-ramthun.de \
    --cc=linux-hotplug@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