On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote: > "Shilimkar, Santosh" <santosh.shilimkar@xxxxxx> writes: > > [...] > > > I don't personally like to add features which hardly anybody use and > > fundamentally broken with full kernel. > > Let's keep sane defaults, but not make it unreasonable to tweak eaither. > > I suggest what has already been mentioned. > > Register both timers, but have the sync timer have a higher rating. On > AMxxx where there is no sync timer, GPtimer will be used. > This is another good option, I can change the rating of both the timers. With below description and given understanding/discussion/usability of both the timers, we can reverse the rating, 32K-sync counter = 300 GPTIMER = 250 Considering the fact that, 32k-sync counter is more usable than gptimer on OMAP platform. @"include/linux/clocksource.h" * @rating: rating value for selection (higher is better) * To avoid rating inflation the following * list should give you a guide as to how * to assign your clocksource a rating * 1-99: Unfit for real use * Only available for bootup and testing purposes. * 100-199: Base level usability. * Functional for real use, but not desired. * 200-299: Good. * A correct and usable clocksource. * 300-399: Desired. * A reasonably fast and accurate clocksource. * 400-499: Perfect * The ideal clocksource. A must-use where * available. Thanks, Vaibhav -- 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
