diff options
author | Viresh Kumar <viresh.kumar@linaro.org> | 2013-06-12 12:05:48 +0530 |
---|---|---|
committer | Viresh Kumar <viresh.kumar@linaro.org> | 2013-06-18 13:53:11 +0530 |
commit | dbb8d76e5ed9bb7f33a092f4aa5b28d8b1c872a4 (patch) | |
tree | db52de2f90211017ac35fe88b4e34a9a731f132f /arch/arm/mach-rpc | |
parent | 6866cba3a4fe1d06d6c4493d5c9a8736db4c5459 (diff) | |
download | linux-dbb8d76e5ed9bb7f33a092f4aa5b28d8b1c872a4.tar.gz linux-dbb8d76e5ed9bb7f33a092f4aa5b28d8b1c872a4.tar.bz2 linux-dbb8d76e5ed9bb7f33a092f4aa5b28d8b1c872a4.zip |
cpufreq: tegra: create CONFIG_ARM_TEGRA_CPUFREQ
currently Tegra cpufreq driver gets built based on ARCH_TEGRA, which doesn't
depend on nor select CPU_FREQ itself, so:
select CPU_FREQ_TABLE if CPU_FREQ
... isn't guaranteed to fire.
The correct solution seems to be:
* Add CONFIG_ARM_TEGRA_CPUFREQ to drivers/cpufreq/Kconfig.arm.
* Make that Kconfig option selct CPU_FREQ_TABLE.
* Make that Kconfig option be def_bool ARCH_TEGRA.
* Modify drivers/cpufreq/Makefile to build tegra-cpufreq.c based on that.
* Remove all the cpufreq-related stuff from arch/arm/mach-tegra/Kconfig.
That way, tegra-cpufreq.c can't be built if !CPU_FREQ, and Tegra's
cpufreq works the same way as all the other cpufreq drivers.
This patch does it.
Suggested-by: Stephen Warren <swarren@nvidia.com>
Tested-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'arch/arm/mach-rpc')
0 files changed, 0 insertions, 0 deletions