On 28 August 2013 02:50, Rafael J. Wysocki wrote:
> On Tuesday, August 27, 2013 10:04:52 PM Lan Tianyu wrote:
>> From my understanding.policy->min/max may be modified by some drivers
>> but the user_policy only store user space config and should not be changed
>> by other reason. :)
>
> Yes,
On Tuesday, August 27, 2013 10:04:52 PM Lan Tianyu wrote:
> 2013/8/27 Viresh Kumar :
> > On 26 August 2013 20:53, Lan Tianyu wrote:
> >> So far as I know, it stores some user's config and cpufreq_update_policy()
> >> bases on the data in the struct to start a new policy. Cpu thermal driver
> >>
2013/8/27 Viresh Kumar :
> On 26 August 2013 20:53, Lan Tianyu wrote:
>> So far as I know, it stores some user's config and cpufreq_update_policy()
>> bases on the data in the struct to start a new policy. Cpu thermal driver
>> （/driver/thermal/cpu_cooling.c）also will its value to update freq
On 26 August 2013 20:53, Lan Tianyu wrote:
> So far as I know, it stores some user's config and cpufreq_update_policy()
> bases on the data in the struct to start a new policy. Cpu thermal driver
> （/driver/thermal/cpu_cooling.c）also will its value to update freq policy
> when receive a cpufreq
On 26 August 2013 20:53, Lan Tianyu lantianyu1...@gmail.com wrote:
So far as I know, it stores some user's config and cpufreq_update_policy()
bases on the data in the struct to start a new policy. Cpu thermal driver
（/driver/thermal/cpu_cooling.c）also will its value to update freq policy
when
2013/8/27 Viresh Kumar viresh.ku...@linaro.org:
On 26 August 2013 20:53, Lan Tianyu lantianyu1...@gmail.com wrote:
So far as I know, it stores some user's config and cpufreq_update_policy()
bases on the data in the struct to start a new policy. Cpu thermal driver
On Tuesday, August 27, 2013 10:04:52 PM Lan Tianyu wrote:
2013/8/27 Viresh Kumar viresh.ku...@linaro.org:
On 26 August 2013 20:53, Lan Tianyu lantianyu1...@gmail.com wrote:
So far as I know, it stores some user's config and cpufreq_update_policy()
bases on the data in the struct to start a
On 28 August 2013 02:50, Rafael J. Wysocki r...@sisk.pl wrote:
On Tuesday, August 27, 2013 10:04:52 PM Lan Tianyu wrote:
From my understanding.policy-min/max may be modified by some drivers
but the user_policy only store user space config and should not be changed
by other reason. :)
Yes,
2013/8/26 Rafael J. Wysocki :
> On Monday, August 26, 2013 08:00:52 PM Viresh Kumar wrote:
>> Hi Rafael,
>
> Hi,
>
>> I am almost done with cleanup of drivers and am back at cpufreq core.. :)
>> I got to this structure: struct cpufreq_real_policy;
>>
>> And I am not able to understand what's the
On Monday, August 26, 2013 08:00:52 PM Viresh Kumar wrote:
> Hi Rafael,
Hi,
> I am almost done with cleanup of drivers and am back at cpufreq core.. :)
> I got to this structure: struct cpufreq_real_policy;
>
> And I am not able to understand what's the need for this structure?
> Can you let me
Hi Rafael,
I am almost done with cleanup of drivers and am back at cpufreq core.. :)
I got to this structure: struct cpufreq_real_policy;
And I am not able to understand what's the need for this structure?
Can you let me know? Before I try to get rid of it :)
--
viresh
--
To unsubscribe from
Hi Rafael,
I am almost done with cleanup of drivers and am back at cpufreq core.. :)
I got to this structure: struct cpufreq_real_policy;
And I am not able to understand what's the need for this structure?
Can you let me know? Before I try to get rid of it :)
--
viresh
--
To unsubscribe from
On Monday, August 26, 2013 08:00:52 PM Viresh Kumar wrote:
Hi Rafael,
Hi,
I am almost done with cleanup of drivers and am back at cpufreq core.. :)
I got to this structure: struct cpufreq_real_policy;
And I am not able to understand what's the need for this structure?
Can you let me know?
2013/8/26 Rafael J. Wysocki r...@sisk.pl:
On Monday, August 26, 2013 08:00:52 PM Viresh Kumar wrote:
Hi Rafael,
Hi,
I am almost done with cleanup of drivers and am back at cpufreq core.. :)
I got to this structure: struct cpufreq_real_policy;
And I am not able to understand what's the
14 matches
Mail list logo
