On 11/18/2012 09:06 AM, Igor Grinberg wrote: > CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way. > Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER > setting. > To remove the dependancy, several conversions/additions had to be done: > 1) Timer initialization functions are named by the platform > name and the clock source in use. > This also makes it possible to define and use the GPTIMER as the > clock source instead of the 32K timer on platforms that do not have > the 32K timer ip block or the 32K timer is not wired on the board. > Cirrently, the the timer is chosen in the machine_desc structure on Nit ... s/Cirrently/Currently Otherwise ... Reviewed-by: Jon Hunter <jon-hunter@xxxxxx> Thanks for updating this! Cheers Jon -- 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
