Dear Myungjoo,
On 01/20/2015 03:59 PM, MyungJoo Ham wrote:
>>
>> Dear Myungjoo,
>>
>> On 01/20/2015 01:34 PM, MyungJoo Ham wrote:
> []
+
+ mutex_lock(&edev->lock);
+ if (edev->desc->ops && edev->desc->ops->enable) {
+ ret = edev->desc->ops->enable(edev);
>>
>
> Dear Myungjoo,
>
>On 01/20/2015 01:34 PM, MyungJoo Ham wrote:
>>>
[]
>>> +
>>> + mutex_lock(&edev->lock);
>>> + if (edev->desc->ops && edev->desc->ops->enable) {
>>> + ret = edev->desc->ops->enable(edev);
>>> + if (ret < 0)
>>> + goto err;
>>> +
Dear Myungjoo,
On 01/20/2015 01:34 PM, MyungJoo Ham wrote:
>>
>> This patch add new devfreq_event class for devfreq_event device which
>> provide
>> raw data (e.g., memory bus utilization/GPU utilization). This raw data from
>> devfreq_event data would be used for the governor of devfreq subs
>
> This patch add new devfreq_event class for devfreq_event device which provide
> raw data (e.g., memory bus utilization/GPU utilization). This raw data from
> devfreq_event data would be used for the governor of devfreq subsystem.
> - devfreq_event device : Provide raw data for governor of e
Dear Myungjoo,
Following patches need to review from you (DEVFREQ maintainer). Please review
these patches.
- [PATCHv8 1/9] devfreq: event: Add new devfreq_event class to provide basic
data for devfreq governor
- [PATCHv8 2/9] devfreq: event: Add resource-managed function for devfreq-event
This patch add new devfreq_event class for devfreq_event device which provide
raw data (e.g., memory bus utilization/GPU utilization). This raw data from
devfreq_event data would be used for the governor of devfreq subsystem.
- devfreq_event device : Provide raw data for governor of existing devfre