On 12/04/2013 12:38 PM, Magnus Damm wrote: > From: Magnus Damm <d...@opensource.se> > > Add Kconfig entries for CMT, MTU2, TMU and STI to > drivers/clocksource/Kconfig. This will allow us to > get rid of duplicated entires in architecture code > such as arch/sh and arch/arm/mach-shmobile. > > Signed-off-by: Magnus Damm <d...@opensource.se> > --- > > drivers/clocksource/Kconfig | 36 ++++++++++++++++++++++++++++++++++++ > 1 file changed, 36 insertions(+) > > --- 0001/drivers/clocksource/Kconfig > +++ work/drivers/clocksource/Kconfig 2013-12-04 22:14:29.000000000 +0900 > @@ -134,3 +134,39 @@ config VF_PIT_TIMER > bool > help > Support for Period Interrupt Timer on Freescale Vybrid Family SoCs. > + > +config SYS_SUPPORTS_CMT > + bool > + > +config SYS_SUPPORTS_TMU > + bool > + > +config SYS_SUPPORTS_MTU2 > + bool > + > +config SYS_SUPPORTS_STI > + bool > + > +config SH_TIMER_CMT > + bool "Renesas CMT timer driver" if COMPILE_TEST > + default SYS_SUPPORTS_CMT > + help > + This enables build of the CMT timer driver. > +
So again, I'd say if this is a non-conflicting COMPILE_TEST option (ie, enabling it doesn't for anything else to be disabled), you might as well enable it without a prompt on COMPILE_TEST. But that's just me. :) If folks really disagree, and there is to be a user prompt, can we get just a little more detail in the help text? So what is the CMT hardware? Maybe what does CMT stand for? What hardware is it frequently found on? thanks -john -- 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/
