On Monday, October 12, 2015 01:11:44 PM Dmitry Torokhov wrote: > On Mon, Oct 12, 2015 at 10:17:05PM +0200, Rafael J. Wysocki wrote: > > On Wednesday, October 07, 2015 03:03:57 AM Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki <[email protected]> > > > > > > If the upcoming system suspend is not going to be handled by the > > > platform firmware, like in the suspend-to-idle case, it is not > > > necessary to reset the controller in i8042_pm_suspend(), so avoid > > > doing that. > > > > > > Moreover, if the system resume currently in progress has not been > > > started by the platform firmware, like in the suspend-to-idle case, > > > i8042_controller_resume() need not be called by i8042_pm_resume(), > > > so avoid doing that too in that case. > > > > > > Additionally, try to catch the event that woke up the system by > > > calling the interrupt handler early during system resume if it has > > > not been started by the platform firmware. > > > > > > Signed-off-by: Rafael J. Wysocki <[email protected]> > > > > If there are no more comments here, I'll tentatively queue it up for v4.4 > > along with the [1-2/3] from this series. > > > > Please let me know if there are any problems with that. > > No problems from my POV. > > Acked-by: Dmitry Torokhov <[email protected]>
Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
