On Sat, 6 Nov 2004, David Brownell wrote: > On Saturday 06 November 2004 14:24, Alan Stern wrote: > > David: > > > > It would be surprising if you weren't already aware of this, but just in > > case you aren't... > > It's always interesting to see if/when bug reports happen; yes. > > I've got patches that resolve this, and I hope to post them soon. > The root cause is "too many notions of root hub state", at least > three ... the fix involves relying on usb_device->state in most > cases, but there are a godawful number of code paths to test > given the various ways to suspend/resume.
Okay, sounds reasonable. Given that dev->power.power_state is being devalued and given that the root hub shouldn't care about the PCI power level (or non-PCI for alternative OHCI implementations!), root_hub->state remains as the only candidate. Once the PM core stuff gets into slightly better shape, it may be necessary to rethink the interface between it and the USB drivers. For instance, we will no longer want to suspend entire subtrees automatically if the PM core does it for us. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
