Re: USB D3 vs system S3

[Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>]

On Wed, 9 Jan 2008, Carlos Corbacho wrote:

> I've had confirmation from another nForce 4 box that Vista also disables 
> autosuspend/ selective suspend on the root hubs there, so I'm pretty 
> confident in saying now that this will also be needed in Linux (definitely 
> for OHCI. I don't think we need to stop autosuspend on EHCI, even though 
> Windows does appear to disable it for that as well), to avoid inadvertently 
> triggering the suspend-to-RAM hang on these broken BIOSs.
> 
> (Testing also shows that putting the OHCI controller into D2 is no good 
> either - having it in any state other than D1 before we call the ACPI _PTS() 
> method will reliably hang the box on suspend).
> 
> What's the best way to go about doing this? I've been glancing over the OHCI 
> code and I can't see how to easily do this (unless 'broken_suspend' is the 
> correct option here?)

Currently there's no need to change anything.

The USB autosuspend code affects only the controller's USB interface -- 
it doesn't touch the PCI side.  An autosuspended controller will remain 
in D0.  Until somebody tries writing autosuspend code for PCI 
devices...

Alan Stern


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel