lkml.org 
[lkml]   [2017]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2 0/8] PM / devfreq: Use OPP interface to handle the frequency
On 2017년 09월 27일 17:09, MyungJoo Ham wrote:
>> Hi Myungjoo,
>>
>> Could you please review this patchset?
>
>
> I ignored your v2 patchset because of the follow-up message:
>
> | Re: [PATCH v2 8/8] PM / devfreq: exynos-bus: Register cooling device
> |
> | Dear all,
> |
> | Please ignore this patch. It has some problem.
> | I'll fix and resend this patch on v2.
>
> I thought you'd send another series with [PATCH v3 x/8]...

I'm sorry. It is my mistake about the ambiguous my comment.
(The 'ignore' comment was only for patch8.)

>
> (I've just noticed that [PATCH v2.1] was sent yesterday.
> Is the patchsetv2 ready with the replacement of 8th commit?)

Yes. I modified the patch8 on 'patch v2.1'.

>
> Cheers,
> MyungJoo
>
> ps. you know I'm going to be away for a long vacation
> starting this week.
> I can't gurantee that I'll see all of the set before the vacation.

I knew of the vacation. Thanks for reply.

Regards,
Chanwoo Choi


>
>>
>> On 2017년 09월 21일 09:33, Chanwoo Choi wrote:
>>> These patches makes the devfreq to use the OPP interface and clean-up codes.
>>> - patch 1~5 are related to the OPP interfaces.
>>> - patch 6 removes the unneeded code.
>>> - patch 7 clean-up for the governor name.
>>> - patch 8 registers the cooling device for exynos-bus.
>>>
>>> [Detaild Descripion]
>>> The commit a76caf55e5b3 ("thermal: Add devfreq cooling") provides
>>> the devfreq cooling device by using the OPP interface such as
>>> dev_pm_opp_disable() and dev_pm_opp_enable(). It means that
>>> the OPP interface is able to change the available status of the frequency.
>>>
>>> Firstly, the existing devfreq doesn't use the OPP interface when showing
>>> the minimum and maximum frequency through the following sysfs nodes:
>>> It shows the wrong frequency value because min_freq/max_freq don't
>>> consider the frequency status by handling OPP interface
>>> (opp_dev_pm_opp_{disable|add}()). So, these patches fix this issue.
>>> - /sys/class/devfreq/devfreqX/min_freq
>>> - /sys/class/devfreq/devfreqX/max_freq
>>>
>>> Second, the 'available_frequencies' should show the all supported frequencis
>>> even if the specific frequency is not available. It doesn't matter whether
>>> frequneyc is available or not. Because the role of 'available_frequencies'
>>> shows the all frequencies. Also, these patches fix this issue.
>>> - /sys/class/devfreq/devfreqX/available_frequencies
>>>
>>> Third, update_devfreq() get the available next frequency by using
>>> the devfreq_recommended_opp() in order to consider the disabled OPP.
>
>
>

\
 
 \ /
  Last update: 2017-09-27 10:15    [W:0.094 / U:2.840 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site