omap clocksource timer selection: dmtimer OR 32K-Sync timer
Cousson, Benoit
b-cousson at ti.com
Fri Jan 13 10:19:35 EST 2012
On 1/13/2012 1:21 PM, Hiremath, Vaibhav wrote:
> Hi,
>
> In case of AM33xx family of devices, we do not have 32K Sync timer
> (32K Counter) available; and the current implementation is based on
> compile-time option, where clock-source is chosen by something like,
>
> File - arch/arm/mach-omap2/timer.c
>
> #ifdef CONFIG_OMAP_32K_TIMER
> static void __init omap2_gp_clocksource_init(int unused, const char *dummy)
> {
> ...
> }
> #else
> static void __init omap2_gp_clocksource_init(int unused, const char *dummy)
> {
> ...
> }
> #endif
>
>
> But in order to support multi-omap build, we must
> make run-time decision to use the timer for kernel clock-source, either of -
>
> - DMTIMER
> - 32K Sync Timer
>
> The DMTIMER is already migrated to the HWMOD framework, but 32K Timer code
> has not yet migrated to it. So the question here is,
A series was sent to do that by Felipe last year, but we somehow forgot
to rebase it on newer kernel and thus never reposted it.
Benoit
More information about the linux-arm-kernel
mailing list