On Thu, May 21, 2015 at 2:43 PM, Ezequiel Garcia <ezequiel.garcia@xxxxxxxxxx> wrote: > This commit introduces a new config, so the user can choose to enable > the General Purpose Timer based clocksource. This option is required > to have CPUFreq support. > > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@xxxxxxxxxx> > --- > arch/mips/Kconfig | 1 + > arch/mips/pistachio/Kconfig | 13 +++++++++++++ > 2 files changed, 14 insertions(+) > create mode 100644 arch/mips/pistachio/Kconfig > > diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig > index f501665..91f6ca0 100644 > --- a/arch/mips/Kconfig > +++ b/arch/mips/Kconfig > @@ -934,6 +934,7 @@ source "arch/mips/jazz/Kconfig" > source "arch/mips/jz4740/Kconfig" > source "arch/mips/lantiq/Kconfig" > source "arch/mips/lasat/Kconfig" > +source "arch/mips/pistachio/Kconfig" > source "arch/mips/pmcs-msp71xx/Kconfig" > source "arch/mips/ralink/Kconfig" > source "arch/mips/sgi-ip27/Kconfig" > diff --git a/arch/mips/pistachio/Kconfig b/arch/mips/pistachio/Kconfig > new file mode 100644 > index 0000000..97731ea > --- /dev/null > +++ b/arch/mips/pistachio/Kconfig > @@ -0,0 +1,13 @@ > +config PISTACHIO_GPTIMER_CLKSRC > + bool "Enable General Purpose Timer based clocksource" > + depends on MACH_PISTACHIO > + select CLKSRC_PISTACHIO > + select MIPS_EXTERNAL_TIMER Why not just select these in the MACH_PISTACHIO Kconfig entry? Is there any harm in always having the Pistachio GPT enabled?
