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.0912071811300.15701-100000@iolanthe.rowland.org>
Date:	Mon, 7 Dec 2009 18:16:43 -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:

> 
> 
> On Mon, 7 Dec 2009, Alan Stern wrote:
> > 
> > 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".
> 
> Ahh, but the sync vs async would then still matter on resume. No?

That's complicated.  If we assume the devices weren't runtime-suspended 
before the sleep began, then they would automatically resume themselves 
when the controller started transmitting EOF packets.  So in that case 
resume would be fast and async wouldn't matter.

But if the devices were runtime-suspended, then what?  The safest
course is to resume them during the system-wide resume.  In that case
yes, the sync vs async would matter.

And if (as happens on many machines) the firmware messes up the
controller settings during resume, then all the USB devices would have
to be reset -- another slow procedure.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ