On Wed, Dec 26, 2012 at 11:32 AM, amit daniel kachhap
wrote:
>
> On Tue, Dec 18, 2012 at 9:45 PM, Doug Anderson wrote:
> > Amit,
> >
> > On Tue, Dec 18, 2012 at 8:17 PM, amit daniel kachhap
> > wrote:
> >> On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao wrote:
> >>> The cpu_thermal generic thermal
On Wed, Dec 26, 2012 at 11:32 AM, amit daniel kachhap
amit.dan...@samsung.com wrote:
On Tue, Dec 18, 2012 at 9:45 PM, Doug Anderson diand...@chromium.org wrote:
Amit,
On Tue, Dec 18, 2012 at 8:17 PM, amit daniel kachhap
amit.dan...@samsung.com wrote:
On Tue, Dec 18, 2012 at 12:29 AM,
On Tue, Dec 18, 2012 at 9:45 PM, Doug Anderson wrote:
> Amit,
>
> On Tue, Dec 18, 2012 at 8:17 PM, amit daniel kachhap
> wrote:
>> On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao wrote:
>>> The cpu_thermal generic thermal management code has a bug where once
>>> max cpu frequency has been lowered
On Tue, Dec 18, 2012 at 9:45 PM, Doug Anderson diand...@chromium.org wrote:
Amit,
On Tue, Dec 18, 2012 at 8:17 PM, amit daniel kachhap
amit.dan...@samsung.com wrote:
On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao sonny...@chromium.org wrote:
The cpu_thermal generic thermal management code has a
Amit,
On Tue, Dec 18, 2012 at 8:17 PM, amit daniel kachhap
wrote:
> On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao wrote:
>> The cpu_thermal generic thermal management code has a bug where once
>> max cpu frequency has been lowered in sysfs (scaling_max_freq) it is
>> not possible to raise the max
On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao wrote:
> The cpu_thermal generic thermal management code has a bug where once
> max cpu frequency has been lowered in sysfs (scaling_max_freq) it is
> not possible to raise the max back up later. The bug is that the
> notifer gets called by
On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao wrote:
> The cpu_thermal generic thermal management code has a bug where once
> max cpu frequency has been lowered in sysfs (scaling_max_freq) it is
> not possible to raise the max back up later. The bug is that the
> notifer gets called by
The cpu_thermal generic thermal management code has a bug where once
max cpu frequency has been lowered in sysfs (scaling_max_freq) it is
not possible to raise the max back up later. The bug is that the
notifer gets called by __cpufreq_set_policy() before the user policy
max is raised, and is
The cpu_thermal generic thermal management code has a bug where once
max cpu frequency has been lowered in sysfs (scaling_max_freq) it is
not possible to raise the max back up later. The bug is that the
notifer gets called by __cpufreq_set_policy() before the user policy
max is raised, and is
On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao sonny...@chromium.org wrote:
The cpu_thermal generic thermal management code has a bug where once
max cpu frequency has been lowered in sysfs (scaling_max_freq) it is
not possible to raise the max back up later. The bug is that the
notifer gets
On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao sonny...@chromium.org wrote:
The cpu_thermal generic thermal management code has a bug where once
max cpu frequency has been lowered in sysfs (scaling_max_freq) it is
not possible to raise the max back up later. The bug is that the
notifer gets
Amit,
On Tue, Dec 18, 2012 at 8:17 PM, amit daniel kachhap
amit.dan...@samsung.com wrote:
On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao sonny...@chromium.org wrote:
The cpu_thermal generic thermal management code has a bug where once
max cpu frequency has been lowered in sysfs (scaling_max_freq)
12 matches
Mail list logo