ARM: OMAP2+: am33xx: Make am33xx as a separate class
authorVaibhav Hiremath <hvaibhav@ti.com>
Thu, 5 Jul 2012 15:05:15 +0000 (08:05 -0700)
committerTony Lindgren <tony@atomide.com>
Thu, 5 Jul 2012 15:05:15 +0000 (08:05 -0700)
commit1c213ba16ed8f48fc12dfec8a588d608ffef0904
treee121a5f4fa9a2f99e28ca8abc3fb9b42e9e2465e
parent353cec46d50a38e412112e23f9542c3d6e51a308
ARM: OMAP2+: am33xx: Make am33xx as a separate class

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.

Please refer to the link below, for mailing-list discussion on this -

http://www.spinics.net/lists/linux-omap/msg69439.html

Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: Kevin Hilman <khilman@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
[tony@atomide.com: fixed typo, updated for soc_is changes]
Signed-off-by: Tony Lindgren <tony@atomide.com>
arch/arm/mach-omap2/Kconfig
arch/arm/mach-omap2/Makefile
arch/arm/mach-omap2/common.c
arch/arm/plat-omap/include/plat/cpu.h
arch/arm/plat-omap/sram.c