[RESEND PATCH] ARM: OMAP2+: am33xx: Make am33xx as a separate class
hvaibhav at ti.com
Tue Jul 10 04:38:35 EDT 2012
On Thu, Jul 05, 2012 at 20:57:43, Tony Lindgren wrote:
> * Tony Lindgren <tony at atomide.com> [120704 01:20]:
> > * Tony Lindgren <tony at atomide.com> [120704 00:29]:
> > > * Vaibhav Hiremath <hvaibhav at ti.com> [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.
Can we clean these branches; it is very confusing to track with so many
Also, One patch still has not merged is,
[PATCH-V2] ARM: OMAP: cpu: Make cpu_class_is_omap2 true for all non-omap1 platforms
Do you have any comments on this? If not, can you merge it?
More information about the linux-arm-kernel