lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <036a01c7d5e2$80add6b0$03c8a8c0@kroptech.com>
Date:	Fri, 3 Aug 2007 11:25:19 -0400
From:	"Adam Kropelin" <akropel1@...hester.rr.com>
To:	"Dave Jones" <davej@...hat.com>, "Jiri Kosina" <jikos@...os.cz>
Cc:	"Matthew Garrett" <mjg59@...f.ucam.org>,
	"Oliver Neukum" <oliver@...kum.org>,
	"Rogan Dawes" <lists@...es.za.net>, "Greg KH" <gregkh@...e.de>,
	<linux-kernel@...r.kernel.org>,
	"David Brownell" <david-b@...bell.net>,
	"Alan Stern" <stern@...land.harvard.edu>,
	<linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] [PATCH] USB: Only enable autosuspend by default on certain device classes

Dave Jones wrote:
> On Fri, Aug 03, 2007 at 04:43:16PM +0200, Jiri Kosina wrote:
>> On Fri, 3 Aug 2007, Matthew Garrett wrote:
>>
>>> Windows will autosuspend hubs, bluetooth devices, HID devices
>>
>> Hi Matthew,
>>
>> are you sure about windows suspending the HID devices in runtime? I
>> have never seen LEDs of USB keyboard connected to windows host to go
>> off after some time of not using it.
>
> Not so sure about keyboards, but I've seen the LEDs on USB mice dim
> or go off after a few seconds of inactivity under Windows, but under
> Linux they stay on.
>
>> We have been playing with runtime autosuspend of HID devices, are
>> currently postponed the full support, as it turns out that many
>> devices don't support this feature properly (probably due to not
>> being tested in Windows).
>
> Interesting.  Which devices did you notice failing?
> Was it a case that they would sleep and not come back out of that
> state?

Although I have no proof immediately at hand, I suspect at a minimum HID 
power class devices should be blacklisted from autosuspend. Given the 
spotty USB implementations on many such devices I'd be surprised if 
suspend worked reliably. Plus if you're connected to such a device for 
monitoring purposes you're probably powered by it as well, so you have 
little to gain from suspend even if it works.

--Adam

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ