Hello Sanjeev, On Thu, 3 Sep 2009, Premi, Sanjeev wrote: > Here, I am proposing a common mechanism to identify the si revision; that focuses > on the revision bits alone. (See code below) > > The usage would then be (example): > > if (omap_rev() > OMAP3430_REV_ES1_0) > > To > > if (cpu_is_omap34xx() && OMAP_REV_GT(OMAP_ES_1_0) For use in structures like clock34xx.h and powerdomains34xx.h, would you propose that we use two different fields then - one for OMAP type, the other for revision restrictions? Or a different scheme? - Paul -- 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
