diff options
| author | Viresh Kumar <viresh.kumar@linaro.org> | 2014-06-10 10:39:46 +0530 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2014-06-10 22:52:35 +0200 |
| commit | 5fbfbcd3e842ddfe9dbbe8865feba909963a87ec (patch) | |
| tree | bff6af59d0758432147ba070ec7b41c9277ae627 /drivers/cpufreq/Kconfig | |
| parent | 40cc5490132075d7be85a4483caa0a7264f45ed4 (diff) | |
| download | linux-5fbfbcd3e842ddfe9dbbe8865feba909963a87ec.tar.gz linux-5fbfbcd3e842ddfe9dbbe8865feba909963a87ec.tar.bz2 linux-5fbfbcd3e842ddfe9dbbe8865feba909963a87ec.zip | |
cpufreq: cpufreq-cpu0: remove dependency on THERMAL and REGULATOR
cpufreq-cpu0 uses thermal framework to register a cooling device, but doesn't
depend on it as there are dummy calls provided by thermal layer when
CONFIG_THERMAL=n. And when these calls fail, the driver is still usable.
Similar explanation is valid for regulators as well. We do have dummy calls
available for regulator APIs and the driver can work even when those calls
fail.
So, we don't really need to mention thermal and regulators as a dependency for
cpufreq-cpu0 in Kconfig as platforms without support for thermal/regulator can
also use this driver. Remove this dependency.
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/Kconfig')
| -rw-r--r-- | drivers/cpufreq/Kconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig index 1fbe11f2a146..e473d6555f96 100644 --- a/drivers/cpufreq/Kconfig +++ b/drivers/cpufreq/Kconfig @@ -185,7 +185,7 @@ config CPU_FREQ_GOV_CONSERVATIVE config GENERIC_CPUFREQ_CPU0 tristate "Generic CPU0 cpufreq driver" - depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL + depends on HAVE_CLK && OF select PM_OPP help This adds a generic cpufreq driver for CPU0 frequency management. |