Re: [PATCH] [CPUFREQ] EXYNOS: Initialize locking_frequency with initial frequency

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Dave,

On 02/09/2012 10:12 AM, Tushar Behera wrote:
> Ping
> 
> On 02/01/2012 04:38 PM, Tushar Behera wrote:
>> Ping
>>
>> On 01/25/2012 10:15 AM, Tushar Behera wrote:
>>> As per definition, locking_frequency is the initial frequency which is
>>> set by boot-loader. Hence the value is updated with the initial value
>>> during boot time init call.
>>>
>>> This code was present in exynos210-cpufreq.c before this consolidation
>>> patch.
>>> - a125a17fa61a ([CPUFREQ] EXYNOS: Make EXYNOS common cpufreq driver).
>>>
>>> Signed-off-by: Tushar Behera <tushar.behera@xxxxxxxxxx>
>>> Signed-off-by: Inderpal Singh <inderpal.singh@xxxxxxxxxx>
>>> ---
>>> The patch is based on v3.3-rc1.
>>>
>>>  drivers/cpufreq/exynos-cpufreq.c |    2 ++
>>>  1 files changed, 2 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c
>>> index 5467879..7cfb516 100644
>>> --- a/drivers/cpufreq/exynos-cpufreq.c
>>> +++ b/drivers/cpufreq/exynos-cpufreq.c
>>> @@ -210,6 +210,8 @@ static int exynos_cpufreq_cpu_init(struct cpufreq_policy *policy)
>>>  
>>>  	cpufreq_frequency_table_get_attr(exynos_info->freq_table, policy->cpu);
>>>  
>>> +	locking_frequency = exynos_getspeed(0);
>>> +
>>>  	/* set the transition latency value */
>>>  	policy->cpuinfo.transition_latency = 100000;
>>>  
>>
>>
> 
> 

Any concerns with this patch?

-- 
Tushar Behera
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Devel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Forum]     [Linux SCSI]

  Powered by Linux