Hi! > > > of them with -EAGAIN, a rather inappropriate > > > response. Perhaps the best course is to accept them, and resume the HC if > > > it's necessary to call the hub_control routine. Under normal > > > circumstances, such as preparing for a system suspend, there shouldn't be > > > any such URBs. (Although there might be a few since the suspend call > > > won't be synchronized with the hub driver.) > > > > I'd rather have these act the same regardless of > > whether USB_SUSPEND is set. Autoresume sounds good, > > going along with autosuspend mechanisms. > > But you don't want autoresume kicking in during a system suspend! It's > not obvious how to prevent such a thing, apart from guaranteeing that no > URBs are submitted. Maybe this is a job for in_system_suspend()... Well, all the problems can be solved by in_system_suspend(), it is just going to be very ugly (remember the patches where I set system_state global and acted accordingly?). Avoid in_system_suspend(), except for debugging etc. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
