On Fri, 29 Aug 2003, David Brownell wrote:
Alan Stern wrote:
usb_hcd_pci_suspend() checks that hcd->state isn't already SUSPENDED or HALT. If not, it calls driver->suspend() and then sets hcd->state to SUSPENDED.
That does sort of "know" that the only non-running states are SUSPENDED and HALT, yes ... and also, that the request isn't going to be vetoed.
I can understand wanting either the glue or the hcd to be able to veto suspending. Does vetoing work yet? I can't suspend at all, because of at least the IDE problems.
I have no idea. I was able to suspend successfully as of a few months ago; haven't tried it recently. Hint: Don't try to suspend if you're running an SMP kernel!
Near as I can tell, the consensus is that 2.6.0-test4 is essentially unusable for PM work, unless maybe your system was already working with ACPI.
When we veto suspends, then the reset() call should work a bit differently. But we're not there yet.
I'm not following you. What's the connection between reset() and vetoing a suspend?
Typo, should have said suspend().
- Dave
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
