[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1431074699.13593.4.camel@x220>
Date: Fri, 08 May 2015 10:44:59 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Lee Jones <lee.jones@...aro.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel@...inux.com, devicetree@...r.kernel.org,
daniel.lezcano@...aro.org, tglx@...utronix.de, wim@...ana.be,
a.zummo@...ertech.it, linux-watchdog@...r.kernel.org,
rtc-linux@...glegroups.com, linux@...ck-us.net
Subject: Re: [PATCH 03/12] clocksource: sti: Provide 'use timer as sched
clock' capability
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?
Thanks,
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists