summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq/longhaul.c
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2013-08-06 22:53:11 +0530
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-08-10 03:24:47 +0200
commit6eed9404ab3c4baea54ce4c7e862e69df1d39f38 (patch)
tree92a27a7908110c7bba019c46e5d3427b6dee42fe /drivers/cpufreq/longhaul.c
parentfe492f3f0332e23cc6ca4913e5a2ed78e1888902 (diff)
downloadop-kernel-dev-6eed9404ab3c4baea54ce4c7e862e69df1d39f38.zip
op-kernel-dev-6eed9404ab3c4baea54ce4c7e862e69df1d39f38.tar.gz
cpufreq: Use rwsem for protecting critical sections
Critical sections of the cpufreq core are protected with the help of the driver module owner's refcount, which isn't the correct approach, because it causes rmmod to return an error when some routine has updated that refcount. Let's use rwsem for this purpose instead. Only cpufreq_unregister_driver() will use write sem and everybody else will use read sem. [rjw: Subject & changelog] Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/longhaul.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud