* [PATCH v3] cpufreq: Kconfig.arm: Fix unmet direct dependencies
@ 2014-02-18 13:44 Fabio Estevam
2014-02-19 5:51 ` Viresh Kumar
0 siblings, 1 reply; 2+ messages in thread
From: Fabio Estevam @ 2014-02-18 13:44 UTC (permalink / raw)
To: rjw; +Cc: viresh.kumar, shawn.guo, linux-pm, festevam, Fabio Estevam
Currently the following warning is generated when building multi_v7_defconfig:
$ make multi_v7_defconfig
warning: (ARM_HIGHBANK_CPUFREQ) selects GENERIC_CPUFREQ_CPU0 which has unmet direct dependencies (ARCH_HAS_CPUFREQ && CPU_FREQ && HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL)
# configuration written to .config
Instead of forcing the selection of GENERIC_CPUFREQ_CPU0 let's depend on it.
By depending on GENERIC_CPUFREQ_CPU0 we can remove the selection of PM_OPP
and REGULATOR because we have:
config GENERIC_CPUFREQ_CPU0
tristate "Generic CPU0 cpufreq driver"
depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL
select PM_OPP
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
Changes since v2:
- Only keep the 'depends on GENERIC_CPUFREQ_CPU0' and remove the other
selections
Changes since v1:
- Use 'depends on'
drivers/cpufreq/Kconfig.arm | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
index 3129749..c43e2c2 100644
--- a/drivers/cpufreq/Kconfig.arm
+++ b/drivers/cpufreq/Kconfig.arm
@@ -84,9 +84,7 @@ config ARM_EXYNOS_CPU_FREQ_BOOST_SW
config ARM_HIGHBANK_CPUFREQ
tristate "Calxeda Highbank-based"
depends on ARCH_HIGHBANK
- select GENERIC_CPUFREQ_CPU0
- select PM_OPP
- select REGULATOR
+ depends on GENERIC_CPUFREQ_CPU0
default m
help
--
1.8.1.2
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v3] cpufreq: Kconfig.arm: Fix unmet direct dependencies
2014-02-18 13:44 [PATCH v3] cpufreq: Kconfig.arm: Fix unmet direct dependencies Fabio Estevam
@ 2014-02-19 5:51 ` Viresh Kumar
0 siblings, 0 replies; 2+ messages in thread
From: Viresh Kumar @ 2014-02-19 5:51 UTC (permalink / raw)
To: Fabio Estevam
Cc: Rafael J. Wysocki, Shawn Guo, linux-pm@vger.kernel.org, festevam
On 18 February 2014 19:14, Fabio Estevam <fabio.estevam@freescale.com> wrote:
> Currently the following warning is generated when building multi_v7_defconfig:
>
> $ make multi_v7_defconfig
> warning: (ARM_HIGHBANK_CPUFREQ) selects GENERIC_CPUFREQ_CPU0 which has unmet direct dependencies (ARCH_HAS_CPUFREQ && CPU_FREQ && HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL)
> # configuration written to .config
>
> Instead of forcing the selection of GENERIC_CPUFREQ_CPU0 let's depend on it.
>
> By depending on GENERIC_CPUFREQ_CPU0 we can remove the selection of PM_OPP
> and REGULATOR because we have:
>
> config GENERIC_CPUFREQ_CPU0
> tristate "Generic CPU0 cpufreq driver"
> depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL
> select PM_OPP
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> Changes since v2:
> - Only keep the 'depends on GENERIC_CPUFREQ_CPU0' and remove the other
> selections
> Changes since v1:
> - Use 'depends on'
>
> drivers/cpufreq/Kconfig.arm | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index 3129749..c43e2c2 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -84,9 +84,7 @@ config ARM_EXYNOS_CPU_FREQ_BOOST_SW
> config ARM_HIGHBANK_CPUFREQ
> tristate "Calxeda Highbank-based"
> depends on ARCH_HIGHBANK
> - select GENERIC_CPUFREQ_CPU0
> - select PM_OPP
> - select REGULATOR
> + depends on GENERIC_CPUFREQ_CPU0
>
> default m
> help
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-02-19 5:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-18 13:44 [PATCH v3] cpufreq: Kconfig.arm: Fix unmet direct dependencies Fabio Estevam
2014-02-19 5:51 ` Viresh Kumar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).