On 7 November 2012 14:54, Zhang Rui wrote:
> On Tue, 2012-10-30 at 17:48 +0100, hongbo.zhang wrote:
>> From: "hongbo.zhang"
>>
>> Problem of using this list is that the cpufreq_get_max_state callback will be
>> called when register cooling device by thermal_cooling_device_register, but
>> this
On 7 November 2012 14:54, Zhang Rui rui.zh...@intel.com wrote:
On Tue, 2012-10-30 at 17:48 +0100, hongbo.zhang wrote:
From: hongbo.zhang hongbo.zh...@linaro.com
Problem of using this list is that the cpufreq_get_max_state callback will be
called when register cooling device by
On Tue, 2012-10-30 at 17:48 +0100, hongbo.zhang wrote:
> From: "hongbo.zhang"
>
> Problem of using this list is that the cpufreq_get_max_state callback will be
> called when register cooling device by thermal_cooling_device_register, but
> this list isn't ready at this moment. What's more, there
On Tue, 2012-10-30 at 17:48 +0100, hongbo.zhang wrote:
From: hongbo.zhang hongbo.zh...@linaro.com
Problem of using this list is that the cpufreq_get_max_state callback will be
called when register cooling device by thermal_cooling_device_register, but
this list isn't ready at this moment.
From: "hongbo.zhang"
Problem of using this list is that the cpufreq_get_max_state callback will be
called when register cooling device by thermal_cooling_device_register, but
this list isn't ready at this moment. What's more, there is no need to maintain
such a list, we can get
From: hongbo.zhang hongbo.zh...@linaro.com
Problem of using this list is that the cpufreq_get_max_state callback will be
called when register cooling device by thermal_cooling_device_register, but
this list isn't ready at this moment. What's more, there is no need to maintain
such a list, we can
6 matches
Mail list logo
