On Fri, 08 May 2015, Paul Bolle wrote: > On Thu, 2015-05-07 at 14:38 +0100, Lee Jones wrote: > > --- a/drivers/clocksource/Kconfig > > +++ b/drivers/clocksource/Kconfig > > > +config CLKSRC_ST_LPC_TIMER_SCHED_CLOCK > > + bool > > + depends on CLKSRC_ST_LPC > > + default y > > + help > > + Use Low Power controller timer clock source as sched_clock > > This adds, as far as I can see, a Kconfig symbol that will always be in > lockstep with CLKSRC_ST_LPC. Ie, CLKSRC_ST_LPC and > CLKSRC_ST_LPC_TIMER_SCHED_CLOCK will always both be 'n' or both be 'y'. > > Are there plans to break that lockstep in the future?
What's stopping CONFIG_CLKSRC_ST_LPC_TIMER_SCHED_CLOCK=n? -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
