Okay, let's go back to an earlier point in the discussion. You said that setting state to RUNNING before calling start() might lead to problems with other calls being passed through too early, before the hardware was running properly. So what other calls might get sent through?
What I said was:
That might work. Now that we have reset(), it might actually make sense to change hcd->state to RUNNING before start() ... requiring the HCD to call usb_hc_died() as soon as it fails. At least, so long as no other task could be expecting all RUNNING hosts to be operational ... it's the fault handling that make me hesitate to change such stuff. And the way that the "dead HC" cleanup isn't yet integrated much with khubd.
That "so long as ..." is what I think you're pursuing here: that's true now, I said it could work so long as that stays true. If you want to change this, just be sure the fault paths behave.
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.
- Dave
...
Put it all together and there doesn't appear to be a problem.
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
