| Message ID | 1431560196-5722-2-git-send-email-tony@atomide.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On 14 May 2015 at 01:36, Tony Lindgren <tony@atomide.com> wrote: > If we don't update last_busy in rpm_resume, devices can go back > to sleep immediately after resume. This happens at least in > cases where the device has been powered off and does not have > any interrupt pending until there's something in the FIFO. > > Signed-off-by: Tony Lindgren <tony@atomide.com> If it's not too late, Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org> Kind regards Uffe -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c index 5070c4f..4ffe4a2 100644 --- a/drivers/base/power/runtime.c +++ b/drivers/base/power/runtime.c @@ -741,6 +741,7 @@ static int rpm_resume(struct device *dev, int rpmflags) } else { no_callback: __update_runtime_status(dev, RPM_ACTIVE); + pm_runtime_mark_last_busy(dev); if (parent) atomic_inc(&parent->power.child_count); }
If we don't update last_busy in rpm_resume, devices can go back to sleep immediately after resume. This happens at least in cases where the device has been powered off and does not have any interrupt pending until there's something in the FIFO. Signed-off-by: Tony Lindgren <tony@atomide.com> --- drivers/base/power/runtime.c | 1 + 1 file changed, 1 insertion(+)