On Tue, 2014-10-21 at 08:59 +0000, Yuantian Tang wrote: > > > -config PPC_CORENET_CPUFREQ > > > - tristate "CPU frequency scaling driver for Freescale E500MC SoCs" > > > - depends on PPC_E500MC && OF && COMMON_CLK > > > +config QORIQ_CPUFREQ > > > + tristate "CPU frequency scaling driver for Freescale QorIQ SoCs" > > > + depends on OF && COMMON_CLK > > > select CLK_PPC_CORENET > > > help > > > - This adds the CPUFreq driver support for Freescale e500mc, > > > - e5500 and e6500 series SoCs which are capable of changing > > > - the CPU's frequency dynamically. > > > + This adds the CPUFreq driver support for Freescale QorIQ SoCs > > > + which are capable of changing the CPU's frequency dynamically. > > > > > > config CPU_FREQ_PMAC > > > bool "Support for Apple PowerBooks" > > > > Don't need this duplication at all. Just move this to Kconfig instead of > > .arm and > > ppc. > > > If I do so, menuconfig will display like this(on PPC): > PowerPC CPU frequency scaling drivers ---- > QorIQ CPU Frequency scaling ---> > <*> CPU frequency scaling driver for Freescale QorIQ SoCs > On ARM, there should be a similar problem. > Isn't weird?
What purpose do those "<arch> CPU frequency scaling drivers" submenus serve, versus just including the options in the main cpufreq menu? It's not as if more than one arch would be visible at once (and when a situation with multiple visible menus popped up, it was considered a bug). -Scott -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
