2005-11-10 14:26:51 +00:00
|
|
|
#
|
|
|
|
# Makefile for the linux kernel.
|
|
|
|
#
|
|
|
|
|
|
|
|
# Common support
|
2011-03-29 22:54:50 +00:00
|
|
|
obj-y := id.o io.o control.o mux.o devices.o serial.o gpmc.o timer.o pm.o \
|
2012-05-08 17:34:27 +00:00
|
|
|
common.o gpio.o dma.o wd_timer.o display.o i2c.o hdq1w.o
|
2009-05-25 18:26:47 +00:00
|
|
|
|
2012-07-05 15:05:15 +00:00
|
|
|
omap-2-3-common = irq.o
|
2010-02-23 05:09:34 +00:00
|
|
|
hwmod-common = omap_hwmod.o \
|
2010-02-24 19:05:58 +00:00
|
|
|
omap_hwmod_common_data.o
|
2010-01-27 03:13:03 +00:00
|
|
|
clock-common = clock.o clock_common_data.o \
|
2010-12-22 03:01:20 +00:00
|
|
|
clkt_dpll.o clkt_clksel.o
|
2012-02-06 10:19:47 +00:00
|
|
|
secure-common = omap-smc.o omap-secure.o
|
OMAP3/4 clock: split into per-chip family files
clock34xx_data.c now contains data for the OMAP34xx family, the
OMAP36xx family, and the OMAP3517 family, so rename it to
clock3xxx_data.c. Rename clock34xx.c to clock3xxx.c, and move the
chip family-specific clock functions to clock34xx.c, clock36xx.c, or
clock3517.c, as appropriate. So now "clock3xxx.*" refers to the OMAP3
superset.
The main goal here is to prepare to compile chip family-specific clock
functions only for kernel builds that target that chip family. To get to
that point, we also need to add CONFIG_SOC_* options for those other
chip families; that will be done in future patches, planned for 2.6.35.
OMAP4 is also affected by this. It duplicated the OMAP3 non-CORE DPLL
clkops structure. The OMAP4 variant of this clkops structure has been
removed, and since there was nothing else currently in clock44xx.c, it
too has been removed -- it can always be added back later when there
is some content for it. (The OMAP4 clock autogeneration scripts have been
updated accordingly.)
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Benoît Cousson <b-cousson@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Ranjith Lohithakshan <ranjithl@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
2010-02-23 05:09:20 +00:00
|
|
|
|
2012-02-06 10:19:47 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += $(omap-2-3-common) $(hwmod-common)
|
2011-06-06 12:26:49 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += prm44xx.o $(hwmod-common) $(secure-common)
|
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>
2012-07-05 15:05:15 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += irq.o $(hwmod-common)
|
2012-06-05 10:51:32 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP5) += prm44xx.o $(hwmod-common) $(secure-common)
|
2005-11-10 14:26:51 +00:00
|
|
|
|
2012-03-09 08:23:27 +00:00
|
|
|
ifneq ($(CONFIG_SND_OMAP_SOC_MCBSP),)
|
|
|
|
obj-y += mcbsp.o
|
|
|
|
endif
|
2008-07-03 09:24:40 +00:00
|
|
|
|
2010-12-10 17:21:05 +00:00
|
|
|
obj-$(CONFIG_TWL4030_CORE) += omap_twl.o
|
2012-07-05 15:05:15 +00:00
|
|
|
obj-$(CONFIG_SOC_HAS_OMAP2_SDRC) += sdrc.o
|
2010-12-10 17:21:05 +00:00
|
|
|
|
2009-04-28 15:22:05 +00:00
|
|
|
# SMP support ONLY available for OMAP4
|
2012-04-28 14:27:32 +00:00
|
|
|
|
2009-04-28 15:22:05 +00:00
|
|
|
obj-$(CONFIG_SMP) += omap-smp.o omap-headsmp.o
|
2010-08-02 10:18:19 +00:00
|
|
|
obj-$(CONFIG_HOTPLUG_CPU) += omap-hotplug.o
|
2012-06-05 10:51:32 +00:00
|
|
|
omap-4-5-common = omap4-common.o omap-wakeupgen.o \
|
|
|
|
sleep44xx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(omap-4-5-common)
|
|
|
|
obj-$(CONFIG_SOC_OMAP5) += $(omap-4-5-common)
|
2010-03-11 07:33:46 +00:00
|
|
|
|
2010-12-01 05:57:51 +00:00
|
|
|
plus_sec := $(call as-instr,.arch_extension sec,+sec)
|
|
|
|
AFLAGS_omap-headsmp.o :=-Wa,-march=armv7-a$(plus_sec)
|
2011-06-06 12:26:49 +00:00
|
|
|
AFLAGS_omap-smc.o :=-Wa,-march=armv7-a$(plus_sec)
|
2010-06-16 16:49:48 +00:00
|
|
|
AFLAGS_sleep44xx.o :=-Wa,-march=armv7-a$(plus_sec)
|
2009-04-28 15:22:05 +00:00
|
|
|
|
2008-07-03 09:24:38 +00:00
|
|
|
# Functions loaded to SRAM
|
2011-01-28 00:39:40 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += sram242x.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += sram243x.o
|
2008-10-09 14:51:41 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += sram34xx.o
|
2008-07-03 09:24:38 +00:00
|
|
|
|
2010-02-12 20:26:46 +00:00
|
|
|
AFLAGS_sram242x.o :=-Wa,-march=armv6
|
|
|
|
AFLAGS_sram243x.o :=-Wa,-march=armv6
|
|
|
|
AFLAGS_sram34xx.o :=-Wa,-march=armv7-a
|
|
|
|
|
2009-12-12 00:16:32 +00:00
|
|
|
# Pin multiplexing
|
2011-01-28 00:39:40 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += mux2420.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += mux2430.o
|
2009-12-12 00:16:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += mux34xx.o
|
2010-08-10 15:27:48 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += mux44xx.o
|
2009-12-12 00:16:32 +00:00
|
|
|
|
2009-01-28 19:27:37 +00:00
|
|
|
# SMS/SDRC
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += sdrc2xxx.o
|
|
|
|
# obj-$(CONFIG_ARCH_OMAP3) += sdrc3xxx.o
|
|
|
|
|
2010-12-09 15:13:46 +00:00
|
|
|
# OPP table initialization
|
|
|
|
ifeq ($(CONFIG_PM_OPP),y)
|
|
|
|
obj-y += opp.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += opp3xxx_data.o
|
2010-12-09 15:13:47 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += opp4xxx_data.o
|
2010-12-09 15:13:46 +00:00
|
|
|
endif
|
|
|
|
|
2006-04-02 16:46:27 +00:00
|
|
|
# Power Management
|
2008-10-06 12:49:15 +00:00
|
|
|
ifeq ($(CONFIG_PM),y)
|
2009-05-28 17:56:16 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += pm24xx.o
|
2011-04-28 22:36:42 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += sleep24xx.o
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += pm34xx.o sleep34xx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += cpuidle34xx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o omap-mpuss-lowpower.o
|
2012-06-05 10:51:32 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP5) += omap-mpuss-lowpower.o
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += cpuidle44xx.o
|
2009-05-28 17:56:16 +00:00
|
|
|
obj-$(CONFIG_PM_DEBUG) += pm-debug.o
|
2010-05-29 16:32:23 +00:00
|
|
|
obj-$(CONFIG_OMAP_SMARTREFLEX) += sr_device.o smartreflex.o
|
2010-05-29 16:32:25 +00:00
|
|
|
obj-$(CONFIG_OMAP_SMARTREFLEX_CLASS3) += smartreflex-class3.o
|
2010-02-12 20:26:46 +00:00
|
|
|
|
|
|
|
AFLAGS_sleep24xx.o :=-Wa,-march=armv6
|
2011-04-26 09:24:50 +00:00
|
|
|
AFLAGS_sleep34xx.o :=-Wa,-march=armv7-a$(plus_sec)
|
2010-02-12 20:26:46 +00:00
|
|
|
|
2009-11-06 03:06:01 +00:00
|
|
|
ifeq ($(CONFIG_PM_VERBOSE),y)
|
|
|
|
CFLAGS_pm_bus.o += -DDEBUG
|
|
|
|
endif
|
|
|
|
|
2008-10-06 12:49:15 +00:00
|
|
|
endif
|
2006-04-02 16:46:27 +00:00
|
|
|
|
2009-09-03 17:14:02 +00:00
|
|
|
# PRCM
|
2012-06-05 10:51:32 +00:00
|
|
|
omap-prcm-4-5-common = prcm.o cminst44xx.o cm44xx.o \
|
|
|
|
prcm_mpu44xx.o prminst44xx.o \
|
|
|
|
vc44xx_data.o vp44xx_data.o
|
2011-12-16 21:36:58 +00:00
|
|
|
obj-y += prm_common.o
|
2010-12-21 22:30:55 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += prcm.o cm2xxx_3xxx.o prm2xxx_3xxx.o
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += prcm.o cm2xxx_3xxx.o prm2xxx_3xxx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += vc3xxx_data.o vp3xxx_data.o
|
2012-06-18 06:47:26 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += prcm.o prm33xx.o cm33xx.o
|
2012-06-05 10:51:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(omap-prcm-4-5-common) prm44xx.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP5) += $(omap-prcm-4-5-common)
|
2011-03-11 05:17:45 +00:00
|
|
|
|
|
|
|
# OMAP voltage domains
|
2011-03-21 21:29:13 +00:00
|
|
|
voltagedomain-common := voltage.o vc.o vp.o
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += $(voltagedomain-common)
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += voltagedomains2xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += $(voltagedomain-common)
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += voltagedomains3xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(voltagedomain-common)
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += voltagedomains44xx_data.o
|
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>
2012-07-05 15:05:15 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += $(voltagedomain-common)
|
2012-06-18 06:47:26 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += voltagedomains33xx_data.o
|
2012-06-05 10:51:32 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP5) += $(voltagedomain-common)
|
2010-12-22 03:01:17 +00:00
|
|
|
|
|
|
|
# OMAP powerdomain framework
|
2010-12-22 03:01:20 +00:00
|
|
|
powerdomain-common += powerdomain.o powerdomain-common.o
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += $(powerdomain-common)
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += powerdomains2xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += powerdomain2xxx_3xxx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += powerdomains2xxx_3xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += $(powerdomain-common)
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += powerdomain2xxx_3xxx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += powerdomains3xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += powerdomains2xxx_3xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(powerdomain-common)
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += powerdomain44xx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += powerdomains44xx_data.o
|
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>
2012-07-05 15:05:15 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += $(powerdomain-common)
|
ARM: OMAP AM33xx: powerdomains: add AM335x support
Add offset & mask fields to struct powerdomain
In case of AM33xx family of devices, there is no consistency between
PWRSTCTRL & PWRSTST register offsers in PRM space, for example -
PRM_XXX PWRSTCTRL PWRSTST
=======================================
PRM_PER_MOD: 0x0C, 0x08
PRM_WKUP_MOD: 0x04, 0x08
PRM_MPU_MOD: 0x00, 0x04
PRM_DEVICE_MOD: NA, NA
And also, there is no consistency between bit-offsets inside
PWRSTCTRL & PWRSTST register, for example -
PRM_XXX LOGICRET MEMON MEMRET
=======================================
GFX_PWRCTRL: 2, 17, 6
PER_PWRCTRL: 3, 25, 29
MPU_PWRCTRL: 2, 18, 22
WKUP_PWRCTRL: 3, NA, NA
This means, we need to maintain and pass on all this information
in powerdomain handle; so adding fields for,
- PWRSTCTRL/ST register offset
- Logic retention state mask
- mem_on/ret/pwrst/retst mask
Currently, this fields is only applicable and used for AM33XX devices.
Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
Cc: Rajendra Nayak <rnayak@ti.com>
[paul@pwsan.com: this patch is a combination of "Add offset & mask fields to
struct powerdomain" and the powerdomain portions of "ARM: OMAP3+: am33xx:
Add powerdomain & PRM support"; updated for 3.5]
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-06-18 06:47:27 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += powerdomain33xx.o
|
|
|
|
obj-$(CONFIG_SOC_AM33XX) += powerdomains33xx_data.o
|
2012-06-05 10:51:32 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP5) += $(powerdomain-common)
|
|
|
|
obj-$(CONFIG_SOC_OMAP5) += powerdomain44xx.o
|
2009-09-03 17:14:02 +00:00
|
|
|
|
2010-12-22 03:01:20 +00:00
|
|
|
# PRCM clockdomain control
|
2012-05-10 16:39:05 +00:00
|
|
|
clockdomain-common += clockdomain.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += $(clockdomain-common)
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += clockdomain2xxx_3xxx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += clockdomains2xxx_3xxx_data.o
|
2011-09-14 22:01:21 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += clockdomains2420_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += clockdomains2430_data.o
|
2012-05-10 16:39:05 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += $(clockdomain-common)
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += clockdomain2xxx_3xxx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += clockdomains2xxx_3xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += clockdomains3xxx_data.o
|
2012-05-10 16:39:05 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(clockdomain-common)
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += clockdomain44xx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += clockdomains44xx_data.o
|
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>
2012-07-05 15:05:15 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += $(clockdomain-common)
|
2012-06-18 06:47:27 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += clockdomain33xx.o
|
|
|
|
obj-$(CONFIG_SOC_AM33XX) += clockdomains33xx_data.o
|
2012-06-05 10:51:32 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP5) += $(clockdomain-common)
|
|
|
|
obj-$(CONFIG_SOC_OMAP5) += clockdomain44xx.o
|
2011-02-25 22:39:28 +00:00
|
|
|
|
2008-03-18 12:41:40 +00:00
|
|
|
# Clock framework
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += $(clock-common) clock2xxx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += clkt2xxx_sys.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += clkt2xxx_dpllcore.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += clkt2xxx_virt_prcm_set.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += clkt2xxx_apll.o clkt2xxx_osc.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += clkt2xxx_dpll.o clkt_iclk.o
|
2011-01-28 00:39:40 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += clock2420_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += clock2430.o clock2430_data.o
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += $(clock-common) clock3xxx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += clock34xx.o clkt34xx_dpll3m2.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += clock3517.o clock36xx.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += dpll3xxx.o clock3xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += clkt_iclk.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(clock-common) clock44xx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += dpll3xxx.o dpll44xx.o
|
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>
2012-07-05 15:05:15 +00:00
|
|
|
obj-$(CONFIG_SOC_AM33XX) += $(clock-common) dpll3xxx.o
|
2012-06-05 10:51:32 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP5) += $(clock-common)
|
|
|
|
obj-$(CONFIG_SOC_OMAP5) += dpll3xxx.o dpll44xx.o
|
OMAP3/4 clock: split into per-chip family files
clock34xx_data.c now contains data for the OMAP34xx family, the
OMAP36xx family, and the OMAP3517 family, so rename it to
clock3xxx_data.c. Rename clock34xx.c to clock3xxx.c, and move the
chip family-specific clock functions to clock34xx.c, clock36xx.c, or
clock3517.c, as appropriate. So now "clock3xxx.*" refers to the OMAP3
superset.
The main goal here is to prepare to compile chip family-specific clock
functions only for kernel builds that target that chip family. To get to
that point, we also need to add CONFIG_SOC_* options for those other
chip families; that will be done in future patches, planned for 2.6.35.
OMAP4 is also affected by this. It duplicated the OMAP3 non-CORE DPLL
clkops structure. The OMAP4 variant of this clkops structure has been
removed, and since there was nothing else currently in clock44xx.c, it
too has been removed -- it can always be added back later when there
is some content for it. (The OMAP4 clock autogeneration scripts have been
updated accordingly.)
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Benoît Cousson <b-cousson@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Ranjith Lohithakshan <ranjithl@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
2010-02-23 05:09:20 +00:00
|
|
|
|
|
|
|
# OMAP2 clock rate set data (old "OPP" data)
|
2011-01-28 00:39:40 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += opp2420_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += opp2430_data.o
|
2008-03-18 12:41:40 +00:00
|
|
|
|
2010-02-23 05:09:32 +00:00
|
|
|
# hwmod data
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += omap_hwmod_2xxx_ipblock_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += omap_hwmod_2xxx_3xxx_ipblock_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += omap_hwmod_2xxx_interconnect_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += omap_hwmod_2xxx_3xxx_interconnect_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += omap_hwmod_2420_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += omap_hwmod_2xxx_ipblock_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += omap_hwmod_2xxx_3xxx_ipblock_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += omap_hwmod_2xxx_interconnect_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += omap_hwmod_2xxx_3xxx_interconnect_data.o
|
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += omap_hwmod_2430_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += omap_hwmod_2xxx_3xxx_ipblock_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += omap_hwmod_2xxx_3xxx_interconnect_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += omap_hwmod_3xxx_data.o
|
2010-05-12 15:54:36 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += omap_hwmod_44xx_data.o
|
2008-03-18 12:41:40 +00:00
|
|
|
|
2009-12-01 13:03:31 +00:00
|
|
|
# EMU peripherals
|
OMAP3/4 clock: split into per-chip family files
clock34xx_data.c now contains data for the OMAP34xx family, the
OMAP36xx family, and the OMAP3517 family, so rename it to
clock3xxx_data.c. Rename clock34xx.c to clock3xxx.c, and move the
chip family-specific clock functions to clock34xx.c, clock36xx.c, or
clock3517.c, as appropriate. So now "clock3xxx.*" refers to the OMAP3
superset.
The main goal here is to prepare to compile chip family-specific clock
functions only for kernel builds that target that chip family. To get to
that point, we also need to add CONFIG_SOC_* options for those other
chip families; that will be done in future patches, planned for 2.6.35.
OMAP4 is also affected by this. It duplicated the OMAP3 non-CORE DPLL
clkops structure. The OMAP4 variant of this clkops structure has been
removed, and since there was nothing else currently in clock44xx.c, it
too has been removed -- it can always be added back later when there
is some content for it. (The OMAP4 clock autogeneration scripts have been
updated accordingly.)
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Benoît Cousson <b-cousson@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Ranjith Lohithakshan <ranjithl@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
2010-02-23 05:09:20 +00:00
|
|
|
obj-$(CONFIG_OMAP3_EMU) += emu.o
|
2009-12-01 13:03:31 +00:00
|
|
|
|
2011-03-07 14:05:20 +00:00
|
|
|
# L3 interconnect
|
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += omap_l3_smx.o
|
2011-03-07 15:23:10 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += omap_l3_noc.o
|
2011-03-07 14:05:20 +00:00
|
|
|
|
2009-11-22 18:11:17 +00:00
|
|
|
obj-$(CONFIG_OMAP_MBOX_FWK) += mailbox_mach.o
|
|
|
|
mailbox_mach-objs := mailbox.o
|
|
|
|
|
2010-05-24 06:35:11 +00:00
|
|
|
obj-$(CONFIG_OMAP_IOMMU) += iommu2.o
|
|
|
|
|
|
|
|
iommu-$(CONFIG_OMAP_IOMMU) := omap-iommu.o
|
|
|
|
obj-y += $(iommu-m) $(iommu-y)
|
2009-01-28 19:32:09 +00:00
|
|
|
|
2010-10-04 16:09:14 +00:00
|
|
|
ifneq ($(CONFIG_TIDSPBRIDGE),)
|
|
|
|
obj-y += dsp.o
|
|
|
|
endif
|
|
|
|
|
2012-05-08 23:23:33 +00:00
|
|
|
# OMAP2420 MSDI controller integration support ("MMC")
|
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += msdi.o
|
|
|
|
|
2005-11-10 14:26:51 +00:00
|
|
|
# Specific board support
|
|
|
|
obj-$(CONFIG_MACH_OMAP_GENERIC) += board-generic.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_H4) += board-h4.o
|
2011-08-23 06:57:23 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP_2430SDP) += board-2430sdp.o
|
2006-04-02 16:46:27 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP_APOLLON) += board-apollon.o
|
2011-08-23 06:57:23 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP3_BEAGLE) += board-omap3beagle.o
|
|
|
|
obj-$(CONFIG_MACH_DEVKIT8000) += board-devkit8000.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_LDP) += board-ldp.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP3530_LV_SOM) += board-omap3logic.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP3_TORPEDO) += board-omap3logic.o
|
|
|
|
obj-$(CONFIG_MACH_ENCORE) += board-omap3encore.o
|
|
|
|
obj-$(CONFIG_MACH_OVERO) += board-overo.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP3EVM) += board-omap3evm.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP3_PANDORA) += board-omap3pandora.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_3430SDP) += board-3430sdp.o
|
2009-08-28 17:51:38 +00:00
|
|
|
obj-$(CONFIG_MACH_NOKIA_N8X0) += board-n8x0.o
|
2012-04-28 14:27:32 +00:00
|
|
|
obj-$(CONFIG_MACH_NOKIA_RM680) += board-rm680.o sdram-nokia.o
|
|
|
|
obj-$(CONFIG_MACH_NOKIA_RX51) += board-rx51.o sdram-nokia.o
|
|
|
|
obj-$(CONFIG_MACH_NOKIA_RX51) += board-rx51-peripherals.o
|
|
|
|
obj-$(CONFIG_MACH_NOKIA_RX51) += board-rx51-video.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_ZOOM2) += board-zoom.o board-zoom-peripherals.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_ZOOM2) += board-zoom-display.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_ZOOM2) += board-zoom-debugboard.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_ZOOM3) += board-zoom.o board-zoom-peripherals.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_ZOOM3) += board-zoom-display.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_ZOOM3) += board-zoom-debugboard.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_3630SDP) += board-3630sdp.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_3630SDP) += board-zoom-peripherals.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP_3630SDP) += board-zoom-display.o
|
2011-08-23 06:57:23 +00:00
|
|
|
obj-$(CONFIG_MACH_CM_T35) += board-cm-t35.o
|
2010-09-21 16:03:09 +00:00
|
|
|
obj-$(CONFIG_MACH_CM_T3517) += board-cm-t3517.o
|
2011-08-23 06:57:23 +00:00
|
|
|
obj-$(CONFIG_MACH_IGEP0020) += board-igep0020.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP3_TOUCHBOOK) += board-omap3touchbook.o
|
2011-11-02 03:11:00 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP_4430SDP) += board-4430sdp.o
|
|
|
|
obj-$(CONFIG_MACH_OMAP4_PANDA) += board-omap4panda.o
|
2011-08-23 06:57:23 +00:00
|
|
|
|
2011-11-02 03:11:00 +00:00
|
|
|
obj-$(CONFIG_MACH_PCM049) += board-omap4pcm049.o
|
2009-03-30 21:58:31 +00:00
|
|
|
|
2011-07-10 09:22:20 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP3517EVM) += board-am3517evm.o
|
2009-11-19 02:41:09 +00:00
|
|
|
|
2010-11-16 22:26:58 +00:00
|
|
|
obj-$(CONFIG_MACH_CRANEBOARD) += board-am3517crane.o
|
|
|
|
|
2011-08-23 06:57:23 +00:00
|
|
|
obj-$(CONFIG_MACH_SBC3530) += board-omap3stalker.o
|
2011-02-15 17:36:08 +00:00
|
|
|
obj-$(CONFIG_MACH_TI8168EVM) += board-ti8168evm.o
|
2011-12-13 18:48:55 +00:00
|
|
|
obj-$(CONFIG_MACH_TI8148EVM) += board-ti8168evm.o
|
2011-08-23 06:57:23 +00:00
|
|
|
|
2009-03-24 01:34:06 +00:00
|
|
|
# Platform specific device init code
|
2011-08-23 06:57:23 +00:00
|
|
|
|
|
|
|
omap-flash-$(CONFIG_MTD_NAND_OMAP2) := board-flash.o
|
|
|
|
omap-flash-$(CONFIG_MTD_ONENAND_OMAP2) := board-flash.o
|
|
|
|
obj-y += $(omap-flash-y) $(omap-flash-m)
|
|
|
|
|
|
|
|
omap-hsmmc-$(CONFIG_MMC_OMAP_HS) := hsmmc.o
|
|
|
|
obj-y += $(omap-hsmmc-m) $(omap-hsmmc-y)
|
|
|
|
|
2009-03-24 01:34:06 +00:00
|
|
|
obj-y += usb-musb.o
|
2011-07-10 09:22:20 +00:00
|
|
|
obj-y += omap_phy_internal.o
|
|
|
|
|
2009-08-28 17:51:37 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP2_TUSB6010) += usb-tusb6010.o
|
2011-03-01 14:38:15 +00:00
|
|
|
obj-y += usb-host.o
|
2009-05-28 20:23:52 +00:00
|
|
|
|
|
|
|
onenand-$(CONFIG_MTD_ONENAND_OMAP2) := gpmc-onenand.o
|
|
|
|
obj-y += $(onenand-m) $(onenand-y)
|
2009-05-28 20:23:52 +00:00
|
|
|
|
2010-02-15 18:03:33 +00:00
|
|
|
nand-$(CONFIG_MTD_NAND_OMAP2) := gpmc-nand.o
|
|
|
|
obj-y += $(nand-m) $(nand-y)
|
|
|
|
|
2009-05-28 20:23:52 +00:00
|
|
|
smc91x-$(CONFIG_SMC91X) := gpmc-smc91x.o
|
|
|
|
obj-y += $(smc91x-m) $(smc91x-y)
|
2010-09-27 16:05:49 +00:00
|
|
|
|
|
|
|
smsc911x-$(CONFIG_SMSC911X) := gpmc-smsc911x.o
|
|
|
|
obj-y += $(smsc911x-m) $(smsc911x-y)
|
2012-03-06 00:11:02 +00:00
|
|
|
ifneq ($(CONFIG_HWSPINLOCK_OMAP),)
|
|
|
|
obj-y += hwspinlock.o
|
|
|
|
endif
|
2011-01-24 06:21:54 +00:00
|
|
|
|
2012-03-05 19:08:36 +00:00
|
|
|
emac-$(CONFIG_TI_DAVINCI_EMAC) := am35xx-emac.o
|
|
|
|
obj-y += $(emac-m) $(emac-y)
|
|
|
|
|
2011-06-04 05:16:41 +00:00
|
|
|
obj-y += common-board-devices.o twl-common.o
|