On Tue, 22 Jul 2008, Dmitry Torokhov wrote: > > 4. From the state (!opened,suspended), calling open fails. Where are we? > > > > Manual suspend will surely cause open to fail. Autosuspend - if > autoresume fails then (closed, unknown) otherwise (closed, > autosuspended - autosuspension may not kick in immediately I think). > > > 5. From the state (opened,suspended), calling resume fails. What state > > are we in? > > > > Screwed up ;) From the driver POV still (opened, suspended) I think. In both of these cases, the final result depends on the reason why the resume failed. If it failed for administrative reasons (such as it was an autoresume and the device had been manually suspended), then the final state is still suspended. But if it fails because the kernel actually tried to resume the device and couldn't do so, then the final state is that the device is gone, logically disconnected. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
