Linux Power Management development
 help / color / mirror / Atom feed
* Re: Re: [PATCH 6/6] PM / devfreq: Set the min_freq and max_freq of devfreq device
@ 2015-11-23  7:21 MyungJoo Ham
  2015-11-23  8:53 ` Chanwoo Choi
  0 siblings, 1 reply; 2+ messages in thread
From: MyungJoo Ham @ 2015-11-23  7:21 UTC (permalink / raw)
  To: 최찬우, 박경민
  Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org

[]
> > 
> > The value 0 is used for min/max_freq to declare
> > that min/max_freq is deactivated. Therefore, it is not
> > required to do so; they are not intended to show the hardware
> > configuration as well.
> 
> This case consider the devfreq device using OPP because devfreq_set_freq_table()
> get the number of OPP entry in OPP list before setting the min_freq/max_freq.
> If the devfreq device don't use the OPP entry, devfreq_set_freq_table()
> will return without any operation.
> 
> IMHO, when devfreq device uses the OPP table including the frequency,
> min_freq/max_freq should show the correct value as CPUFREQ framework.
> 

The side effect of this patch shows up when opp_disable() and opp_enable()
are used.

For example,
1. dev->opp_disable(2GHz); /* 2GHz is the fastest and 1.6 is the second */
2. init devfreq of dev; /* setting max_freq @ 1.6G by this patch */
3. dev->opp_enable(2GHz);
4. 2GHz is still not active because max_freq is now 1.6GHz.

Cheers,
MyungJoo.



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Re: [PATCH 6/6] PM / devfreq: Set the min_freq and max_freq of devfreq device
  2015-11-23  7:21 Re: [PATCH 6/6] PM / devfreq: Set the min_freq and max_freq of devfreq device MyungJoo Ham
@ 2015-11-23  8:53 ` Chanwoo Choi
  0 siblings, 0 replies; 2+ messages in thread
From: Chanwoo Choi @ 2015-11-23  8:53 UTC (permalink / raw)
  To: myungjoo.ham@samsung.com
  Cc: 박경민, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org

On Mon, Nov 23, 2015 at 4:21 PM, MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
> []
>> >
>> > The value 0 is used for min/max_freq to declare
>> > that min/max_freq is deactivated. Therefore, it is not
>> > required to do so; they are not intended to show the hardware
>> > configuration as well.
>>
>> This case consider the devfreq device using OPP because devfreq_set_freq_table()
>> get the number of OPP entry in OPP list before setting the min_freq/max_freq.
>> If the devfreq device don't use the OPP entry, devfreq_set_freq_table()
>> will return without any operation.
>>
>> IMHO, when devfreq device uses the OPP table including the frequency,
>> min_freq/max_freq should show the correct value as CPUFREQ framework.
>>
>
> The side effect of this patch shows up when opp_disable() and opp_enable()
> are used.

Ah. You're right.
I was not considering the the case of using opp_disable() and opp_enable().
I'll consider it again including the usage case of opp_diable/opp_enable.

Regards,
Chanwoo Choi

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-11-23  8:53 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-23  7:21 Re: [PATCH 6/6] PM / devfreq: Set the min_freq and max_freq of devfreq device MyungJoo Ham
2015-11-23  8:53 ` Chanwoo Choi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox