On Tue, 24 Feb 2004, David Brownell wrote:
On the other hand, maybe it'd just be simpler to make the root hub registration code set the state to RUNNING? That would solve your issue of wanting that state change out of the HCDs.
That's a very good idea. Non-PCI HCDs will still have to cope with state, but that's inevitable since they have to start and stop all by themselves.
Can usb_hcd_pci_resume() be changed to set the state to RUNNING whenever the resume() method doesn't return an error? I think that's the only other case where HCDs are forced to change the state.
That might call for some sort of usbcore callback, so HCDs can report they've successfully resumed. But maybe not ... PM resume has worked so poorly for me (because of non-USB issues) that I'm not sure what to think there any more.
- Dave
Alan Stern
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
