linux-kernel - Re: [GIT PULL] PM updates for 2.6.33

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: <Pine.LNX.4.44L0.0912071716080.15701-100000@iolanthe.rowland.org>
Date:	Mon, 7 Dec 2009 17:21:36 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Zhang Rui <rui.zhang@...el.com>, "Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	pm list <linux-pm@...ts.linux-foundation.org>
Subject: Re: [GIT PULL] PM updates for 2.6.33

On Mon, 7 Dec 2009, Linus Torvalds wrote:

> I also suspect that even if you do the USB host controller suspend 
> synchronously, doing the actual USB devices asynchronously would still 
> help - even if it's only "asynchronously per bus" thing. 
> 
> So in fact, it's probably a good first step to start off doing only the 
> USB devices, not the controller.

Interesting you should say that.  The patch I asked Arjan to test 
involved not suspending USB devices at all (root hubs being the 
exception).  That is in fact just what we do when CONFIG_USB_SUSPEND 
isn't set.

There's no need to suspend the individual devices when the whole system 
is going down.  They will automatically suspend when the controller 
stops sending out SOF packets, which occurs when the root hub is 
suspended.  The USB spec describes this, grandiosely, as a "global 
suspend".

But yes, I agree.  Doing just the USB devices is a good first step.

Alan Stern

--
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/