* Tony Lindgren <tony@xxxxxxxxxxx> [120704 01:20]: > * Tony Lindgren <tony@xxxxxxxxxxx> [120704 00:29]: > > * Vaibhav Hiremath <hvaibhav@xxxxxx> [120703 06:12]: > > > 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_AM33XX) under OMAP2PLUS. > > > This means, for am33xx device, cpu_is_omap34xx() will return false, > > > and only cpu_is_am33xx() will be true. > > > > Thanks applying both. > > I believe all your patches are now applied. I've pushed them out > into devel-am33xx-part2 branch. Can you please check and send > additional patches as needed? I ended up moving some patches into cleanup-part2 branch as omap5 patches also need those. So the new branch for am33xx is called devel-am33xx-data at commit 79ab2664. The old devel-am33xx-part2 branch should be ignored now. Regards, 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
