lkml.org 
[lkml]   [2018]   [Dec]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: Re: [PATCH v3 2/5] devfreq: add support for suspend/resume of a devfreq device
From
Date
> Hi Lukasz,
>
> On 2018년 12월 05일 20:05, Lukasz Luba wrote:
> > The patch prepares devfreq device for handling suspend/resume
> > functionality. The new fields will store needed information during this
> > process. Devfreq framework handles opp-suspend DT entry and there is no
> > need of modyfications in the drivers code. It uses atomic variables to
> > make sure no race condition affects the process.
> >
> > Suggested-by: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
> > Suggested-by: Chanwoo Choi <cw00.choi@samsung.com>
> > Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
> > ---
> > drivers/devfreq/devfreq.c | 47 +++++++++++++++++++++++++++++++++++++++++------
> > include/linux/devfreq.h | 7 +++++++
> > 2 files changed, 48 insertions(+), 6 deletions(-)
>
> Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
>

Looks goot do me as well.

Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>


Anyway, for the sake of curiosity...

Having suspend-frequency is usually required when
the frequency configuration is reset with suspend-resume
as older Exynos's CPU did (I don't know whether it still does).

Does GPU do this as well?
(memory-bus won't do this because they are kept turned on during suspend)


Cheers,
MyungJoo


\
 
 \ /
  Last update: 2018-12-11 02:44    [W:0.194 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site