On Tuesday 05 March 2013 18:55:42 Ming Lei wrote: > > All these drivers suspend in multiple steps, where each step can > > fail. If a later step fails then they revert any previously successful > > step before returning the failure, thereby ensuring that the > > device/driver state when suspend returns is consistently either > > suspended or resumed. > > IMO, for autosuspend, that is right, but it is not for system suspend, > and the driver's suspend callback can't return in resumed state > because the USB core will ignore the failure return value and force > to suspend the device. It seems to me that in this case you just need to make sure that suspend() not fail for system suspend. Or revisit the decision to ignore failures. In other words, if we don't handle errors, there must be no errors, otherwise it doesn't matter what we do in the error case. We'd leave the problem to generic layers. Furthermore there is a small chance that although the device tree is walked, teh system suspend fails for another later reason that is not ignored. In that case the drivers need to do error recovery, albeit in resume(). Regards Oliver -- 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
