On 23 August 2012 12:37, MyungJoo Ham wrote:
>> On 20 August 2012 15:15, 함명주 wrote:
>> >> Devfreq returns governor predicted frequency as current
>> >> frequency via sysfs interface. But device may not support
>> >> all frequencies that governor predicts. As per the design
>> >> its driver respon
> On 20 August 2012 15:15, 함명주 wrote:
> >> Devfreq returns governor predicted frequency as current
> >> frequency via sysfs interface. But device may not support
> >> all frequencies that governor predicts. As per the design
> >> its driver responsibility to maintain current frequency
> >> at whic
On 20 August 2012 15:15, 함명주 wrote:
>> Devfreq returns governor predicted frequency as current
>> frequency via sysfs interface. But device may not support
>> all frequencies that governor predicts. As per the design
>> its driver responsibility to maintain current frequency
>> at which device is
> Devfreq returns governor predicted frequency as current
> frequency via sysfs interface. But device may not support
> all frequencies that governor predicts. As per the design
> its driver responsibility to maintain current frequency
> at which device is operating. So add a callback in device
> p
Devfreq returns governor predicted frequency as current
frequency via sysfs interface. But device may not support
all frequencies that governor predicts. As per the design
its driver responsibility to maintain current frequency
at which device is operating. So add a callback in device
profile to fi
