[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191029083222.GA558937@kroah.com>
Date: Tue, 29 Oct 2019 09:32:22 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Ikjoon Jang <ikjn@...omium.org>
Cc: linux-pm@...r.kernel.org, "Rafael J . Wysocki" <rjw@...ysocki.net>,
"Pavel Machek )" <pavel@....cz>, Len Brown <len.brown@...el.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpuidle: undelaying cpuidle in dpm_{suspend|resume}()
On Tue, Oct 29, 2019 at 03:31:45PM +0800, Ikjoon Jang wrote:
> cpuidle is paused only during dpm_suspend_noirq() ~ dpm_resume_noirq().
> But some device drivers need random sized IOs in dpm_{suspend|resume}()
> stage (e.g. re-downloading firmware in resume).
> And with such a device, cpuidle's latencies could be critical to
> response time of system suspend/resume.
>
> To minimize those latencies, we could apply pm_qos to such device drivers,
> but simply undelaying cpuidle from dpm_suspend_noirq() to dpm suspend()
> seems no harm.
> ---
> drivers/base/power/main.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
no signed-off-by?
:(
Powered by blists - more mailing lists