diff options
| author | Nicolas Pitre <nico@fluxnic.net> | 2012-04-18 21:29:58 -0400 |
|---|---|---|
| committer | Dave Martin <dave.martin@linaro.org> | 2012-04-27 17:15:49 +0100 |
| commit | c028288acee7ea9a48a7fa50b78231469b7b57a7 (patch) | |
| tree | 57c5621c0c24d76a2e8bb02a02187175514cb9f4 | |
| parent | 57f4440e90daf565f78b0e14695378956626e08a (diff) | |
cpufreq/arm-bl-cpufreq: remove the forced switch on module removal
Switching all CPUs back to the fast cluster upon driver removal
might be considered a good thing. However this has some
disadvantages such as not allowing for a specific power state to be
left active once the driver is removed. Codewise, special care
would also be needed for this case as the notifiers can't be called
once the driver is unregistered (the code is buggy in that regard
already, oopsing the kernel).
Removing this driver is rather unlikely in practice, and people
doing so should know what they're doing. So the best solution is
probably to just remove the forced switch from the module exit
path.
(Trivially ported over to the reference switcher driver by Dave
Martin.)
Signed-off-by: nicolas Pitre <nico@linaro.org>
Signed-off-by: Dave Martin <dave.martin@linaro.org>
| -rw-r--r-- | drivers/cpufreq/arm-bl-cpufreq_driver.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/cpufreq/arm-bl-cpufreq_driver.c b/drivers/cpufreq/arm-bl-cpufreq_driver.c index 9fbf85167c6..8c669a2df59 100644 --- a/drivers/cpufreq/arm-bl-cpufreq_driver.c +++ b/drivers/cpufreq/arm-bl-cpufreq_driver.c @@ -243,9 +243,6 @@ static void __exit bl_cpufreq_module_exit(void) { cpufreq_unregister_driver(&bl_cpufreq_driver); - /* Restore the "default" cluster: */ - switch_to_entry(find_entry_by_cluster(CLUSTER_BIG)); - pr_info("cpufreq backend driver unloaded.\n"); } module_exit(bl_cpufreq_module_exit); |