* Ran Shalit <ranshalit@xxxxxxxxx> [161219 05:48]: > Hello, > > I'm not sure if hrtimer in omap is supported. > I am using omap4, with kernel 3.4.x, > > But I can't find in configuration support for MPU timer, i.e. it's > seem that my architecture (omap4) does not support it(?): > > Symbol: OMAP_MPU_TIMER [=n] │ > │ Type : boolean │ > │ Prompt: Use mpu timer │ > │ Defined at arch/arm/plat-omap/Kconfig:189 │ > │ Depends on: ARCH_OMAP [=y] && ARCH_OMAP1 [=n] │ > │ Location: │ > │ -> System Type │ > │ -> TI OMAP Common Features │ > │ Selected by: ARCH_OMAP730 [=n] && ARCH_OMAP1 [=n] || ARCH_OMAP15XX [= │ > > Does it mean that I don't have high resolution timer ? No, that's for omap1. For omap4 there are typically two gptimer instances that can be configured with two input sources, typically using the 32KiHz clock as that's always on and works for PM also. See mach-omap2/timer.c Then there are the ARM local timers on omap4 that cpuidle_coupled uses during runtime. See drivers/cpuidle/coupled.c. Then there's the Linux hrtimer code that we're using. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
