Tarun Kanti DebBarma <tarun.ka...@ti.com> writes: > Generation of 1ms granular GPTIMER events using 32KHz or system > clocks as inputs does not have whole number count value to load > into the register. This inaccurate count value with respect to 1ms > period leads to time drift subsequently. OMAP3 and later silicons > have dedicated registers for GPTIMER1, GPTIMER2 and GPTIMER10, > which can be programmed with computed values to keep this error > controlled within specified limit. > > Version 2: > (i) optimized omap_dm_timer_ms_correction() function and corrected > error in computing the positive and negative increments. > (ii) typo corrections in comment section and warning removal related > to 80-character limit > > Tested on Zoom3 using Linus tree. > > Signed-off-by: R Sricharan <r.sricha...@ti.com> > Signed-off-by: Tarun Kanti DebBarma <tarun.ka...@ti.com>
Please coordinate this change with the GPTIMER hwmod changes. The timers that have/need this feature should be flagged at the hwmod level (probably by a dev_attr flag.) Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
