On 30 August 2012 13:42, MyungJoo Ham wrote:
>> On 23 August 2012 09:57, MyungJoo Ham wrote:
>> >> > On 20 August 2012 12:50, 함명주 wrote:
>> >> >
>> >> > > Prepare devfreq core framework to support devices which
>> >> > > can idle. When device idleness is detected perhaps through
>> >> > > runtim
> On 23 August 2012 09:57, MyungJoo Ham wrote:
> >> > On 20 August 2012 12:50, 함명주 wrote:
> >> >
> >> > > Prepare devfreq core framework to support devices which
> >> > > can idle. When device idleness is detected perhaps through
> >> > > runtime-pm, need some mechanism to suspend devfreq load
>
On 23 August 2012 09:57, MyungJoo Ham wrote:
>> > On 20 August 2012 12:50, 함명주 wrote:
>> >
>> > > Prepare devfreq core framework to support devices which
>> > > can idle. When device idleness is detected perhaps through
>> > > runtime-pm, need some mechanism to suspend devfreq load
>> > > monitor
> > On 20 August 2012 12:50, 함명주 wrote:
> >
> > > Prepare devfreq core framework to support devices which
> > > can idle. When device idleness is detected perhaps through
> > > runtime-pm, need some mechanism to suspend devfreq load
> > > monitoring and resume when device is back online. Present
On 20 August 2012 12:50, 함명주 wrote:
>
> > Prepare devfreq core framework to support devices which
> > can idle. When device idleness is detected perhaps through
> > runtime-pm, need some mechanism to suspend devfreq load
> > monitoring and resume when device is back online. Present
> > code contin
On 20 August 2012 12:50, 함명주 wrote:
> > Prepare devfreq core framework to support devices which
> > can idle. When device idleness is detected perhaps through
> > runtime-pm, need some mechanism to suspend devfreq load
> > monitoring and resume when device is back online. Present
> > code continu
> Prepare devfreq core framework to support devices which
> can idle. When device idleness is detected perhaps through
> runtime-pm, need some mechanism to suspend devfreq load
> monitoring and resume when device is back online. Present
> code continues monitoring unless device is removed from
> de
Prepare devfreq core framework to support devices which
can idle. When device idleness is detected perhaps through
runtime-pm, need some mechanism to suspend devfreq load
monitoring and resume when device is back online. Present
code continues monitoring unless device is removed from
devfreq core.