* Kevin Hilman <khilman@xxxxxx> [120508 15:00]: > Vaibhav Hiremath <hvaibhav@xxxxxx> writes: > > > Initially, we decided to make am33xx family of device to fall > > under omap3 class (cpu_is_omap34xx() = true), since it carries > > Cortex-A8 core. But while adding complete baseport support > > (like, clock, power and hwmod) support, it is observed that, > > we are creating more and more problems by treating am33xx device > > as omap3 family, as nothing matches between them > > (except cortex-A8 mpu). > > > > So, after long discussion we have came to the conclusion that, > > we should not consider am33xx device as omap3 family, instead > > create separate class (SOC_OMAPAM33XX) under OMAP2PLUS. > > This means, for am33xx device, cpu_is_omap34xx() will return false, > > and only cpu_is_am33xx() will be true. > > Not directly related to this patch, but does anyone have any objection > to dropping the OMAP from the SOC_ names for AM33xx and TI81XX? > > I'll post a series shortly to do so. No objection. 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
