On 31 July 2013 22:09, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
> On 31 July 2013 22:06, Sachin Kamat <sachin.kamat@xxxxxxxxxx> wrote:
>> Hi Viresh,
>>
>> On 31 July 2013 19:49, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
>>> CPUFreq core does following at multiple places:
>>> module_{get|put}(cpufreq_driver->owner)).
>>>
>>> This is done to make sure module doesn't get unloaded if it is currently in use.
>>> This will work only if the .owner field of cpufreq driver is initialized with a
>>> valid pointer.
>>>
>>> This field wasn't initialized for many cpufreq driver, lets initialize it with
>>> THIS_MODULE.
>>
>>
>> Isn't it possible to do this inside cpufreq_register_driver function
>> in a similar way as done for platform_driver_register [1].
>>
>> [1] https://lkml.org/lkml/2013/5/25/5
>
> Don't know if its possible to set it to something other than THIS_MODULE.
> In which case we want something else to be done.
Even I am curious to know if it is possible to set the owner to
something other than THIS_MODULE.
--
With warm regards,
Sachin
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
