This looks pretty good to me. So you're still relying on the driver's start() and resume() methods to set hcd->state to RUNNING, rather than relying on checking their return codes in hcd-pci.c and doing it for them?
For now, yes. If you're implying that those states should only get set in the hcd glue ... I'm not sure that'd work. There are points in those routines that enable HC IRQs. Since they may arrive immediately, there'd be a race with between IRQ arrival and returning to hcd-pci.c to update the state.
- 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
