http://bugzilla.kernel.org/show_bug.cgi?id=9528
------- Comment #86 from [EMAIL PROTECTED] 2008-01-09 11:01 ------- (In reply to comment #84) > Ok, so after my discussion with Alan Stern: > > 1) At the moment, Linux USB autosuspend doesn't actually suspend the PCI OHCI > controller (i.e. Linux doesn't change its power state), just the ports; so the > issue of the OHCI controller going to D3 behind our backs isn't relevant for > now. Fine. > 2) For the future: > > USB0's _S1D states that the OHCI controller cannot be put into a higher > D-state Please don't use the "higher D-state" language, it's ambiguous. Actually, the USB0's _S1D says that we can put the device in either of D1, D2 and D3 before entering S1. > anyway when in S1 - so when Linux gets round to being able to runtime suspend > USB PCI controllers (as opposed to just the ports), when in S1 we will need to > check _S1D to make sure it is actually safe to go to high D-states (even if we > don't want to do this check for S3) to make sure we don't runtime suspend the > OHCI controller. S1 is a system sleep state (often referred to as standby), it has nothing to do with dynamic pm. > So to summarise: We don't put the OHCI controller into D3 at the moment in S1; Yes, we do, in the same way as we do before entering S3. We don't autosuspend it into D3, which makes quite a difference. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- 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 _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
