Re: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback

2016-02-22 Thread Tomeu Vizoso
On 28 January 2016 at 05:14, MyungJoo Ham wrote: >> Hi Thierry, >> >> On 21 January 2016 at 02:54, Thierry Reding wrote: >> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote: > [] >> >> Signed-off-by: Tomeu Vizoso >> >> Reported-by: Tyler Baker > [] >> >> >> > >> > I had noticed it

Re: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback

2016-01-28 Thread Tyler Baker
On 27 January 2016 at 20:14, MyungJoo Ham wrote: >> Hi Thierry, >> >> On 21 January 2016 at 02:54, Thierry Reding wrote: >> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote: > [] >> >> Signed-off-by: Tomeu Vizoso >> >> Reported-by: Tyler Baker > [] >> >> >> > >> > I had noticed it

Re: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback

2016-01-27 Thread MyungJoo Ham
> Hi Thierry, > > On 21 January 2016 at 02:54, Thierry Reding wrote: > > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote: [] > >> Signed-off-by: Tomeu Vizoso > >> Reported-by: Tyler Baker [] > >> > > > > I had noticed it recently but hadn't got around to look into it, thanks > > fo

Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback

2016-01-27 Thread Tyler Baker
Hi Thierry, On 21 January 2016 at 02:54, Thierry Reding wrote: > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote: >> As per the documentation of the devfreq_dev_profile.target callback, set >> the freq argument to the new frequency before returning. >> >> This caused endless messages

Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback

2016-01-21 Thread Thierry Reding
On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote: > As per the documentation of the devfreq_dev_profile.target callback, set > the freq argument to the new frequency before returning. > > This caused endless messages like this after recent changes in the core: > > devfreq 6000c800.act

Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback

2016-01-21 Thread MyungJoo Ham
>As per the documentation of the devfreq_dev_profile.target callback, set >the freq argument to the new frequency before returning. > >This caused endless messages like this after recent changes in the core: > >devfreq 6000c800.actmon: Couldn't update frequency transition information. > >Signed-off

[PATCH] PM / devfreq: tegra: Set freq in rate callback

2016-01-20 Thread Tomeu Vizoso
As per the documentation of the devfreq_dev_profile.target callback, set the freq argument to the new frequency before returning. This caused endless messages like this after recent changes in the core: devfreq 6000c800.actmon: Couldn't update frequency transition information. Signed-off-by: Tom