2005-11-10 17:26:51 +03:00
#
# Makefile for the linux kernel.
#
# Common support
2011-03-30 02:54:50 +04:00
obj-y := id.o io.o control.o mux.o devices.o serial.o gpmc.o timer.o pm.o \
2012-09-12 05:09:13 +04:00
common.o gpio.o dma.o wd_timer.o display.o i2c.o hdq1w.o omap_hwmod.o
2009-05-25 22:26:47 +04:00
2012-09-12 05:09:14 +04:00
# INTCPS IP block support - XXX should be moved to drivers/
obj-$(CONFIG_ARCH_OMAP2) += irq.o
obj-$(CONFIG_ARCH_OMAP3) += irq.o
obj-$(CONFIG_SOC_AM33XX) += irq.o
# Secure monitor API support
obj-$(CONFIG_ARCH_OMAP3) += omap-smc.o omap-secure.o
obj-$(CONFIG_ARCH_OMAP4) += omap-smc.o omap-secure.o
obj-$(CONFIG_SOC_OMAP5) += omap-smc.o omap-secure.o
2012-03-09 12:23:27 +04:00
i f n e q ( $( CONFIG_SND_OMAP_SOC_MCBSP ) , )
obj-y += mcbsp.o
e n d i f
2008-07-03 13:24:40 +04:00
2012-09-12 05:09:13 +04:00
obj-$(CONFIG_TWL4030_CORE) += omap_twl.o
2010-12-10 20:21:05 +03:00
2009-04-28 19:22:05 +04:00
# SMP support ONLY available for OMAP4
2012-04-28 18:27:32 +04:00
2009-04-28 19:22:05 +04:00
obj-$(CONFIG_SMP) += omap-smp.o omap-headsmp.o
2010-08-02 14:18:19 +04:00
obj-$(CONFIG_HOTPLUG_CPU) += omap-hotplug.o
2012-09-12 05:09:14 +04:00
obj-$(CONFIG_ARCH_OMAP4) += omap4-common.o omap-wakeupgen.o
obj-$(CONFIG_SOC_OMAP5) += omap4-common.o omap-wakeupgen.o
2010-03-11 10:33:46 +03:00
2010-12-01 08:57:51 +03:00
plus_sec := $( call as-instr,.arch_extension sec,+sec)
AFLAGS_omap-headsmp.o := -Wa,-march= armv7-a$( plus_sec)
2011-06-06 16:26:49 +04:00
AFLAGS_omap-smc.o := -Wa,-march= armv7-a$( plus_sec)
2010-06-16 20:49:48 +04:00
AFLAGS_sleep44xx.o := -Wa,-march= armv7-a$( plus_sec)
2009-04-28 19:22:05 +04:00
2008-07-03 13:24:38 +04:00
# Functions loaded to SRAM
2011-01-28 03:39:40 +03:00
obj-$(CONFIG_SOC_OMAP2420) += sram242x.o
obj-$(CONFIG_SOC_OMAP2430) += sram243x.o
2008-10-09 18:51:41 +04:00
obj-$(CONFIG_ARCH_OMAP3) += sram34xx.o
2008-07-03 13:24:38 +04:00
2010-02-12 23:26:46 +03:00
AFLAGS_sram242x.o := -Wa,-march= armv6
AFLAGS_sram243x.o := -Wa,-march= armv6
AFLAGS_sram34xx.o := -Wa,-march= armv7-a
2009-12-12 03:16:32 +03:00
# Pin multiplexing
2011-01-28 03:39:40 +03:00
obj-$(CONFIG_SOC_OMAP2420) += mux2420.o
obj-$(CONFIG_SOC_OMAP2430) += mux2430.o
2009-12-12 03:16:32 +03:00
obj-$(CONFIG_ARCH_OMAP3) += mux34xx.o
2010-08-10 19:27:48 +04:00
obj-$(CONFIG_ARCH_OMAP4) += mux44xx.o
2009-12-12 03:16:32 +03:00
2009-01-28 22:27:37 +03:00
# SMS/SDRC
obj-$(CONFIG_ARCH_OMAP2) += sdrc2xxx.o
# obj-$(CONFIG_ARCH_OMAP3) += sdrc3xxx.o
2012-09-12 05:09:14 +04:00
obj-$(CONFIG_SOC_HAS_OMAP2_SDRC) += sdrc.o
2009-01-28 22:27:37 +03:00
2010-12-09 18:13:46 +03:00
# OPP table initialization
i f e q ( $( CONFIG_PM_OPP ) , y )
obj-y += opp.o
obj-$(CONFIG_ARCH_OMAP3) += opp3xxx_data.o
2010-12-09 18:13:47 +03:00
obj-$(CONFIG_ARCH_OMAP4) += opp4xxx_data.o
2010-12-09 18:13:46 +03:00
e n d i f
2006-04-02 20:46:27 +04:00
# Power Management
2008-10-06 16:49:15 +04:00
i f e q ( $( CONFIG_PM ) , y )
2012-09-12 05:09:14 +04:00
obj-$(CONFIG_ARCH_OMAP2) += pm24xx.o sleep24xx.o
2012-04-28 18:27:32 +04:00
obj-$(CONFIG_ARCH_OMAP3) += pm34xx.o sleep34xx.o
obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o omap-mpuss-lowpower.o
2012-09-12 05:09:14 +04:00
obj-$(CONFIG_ARCH_OMAP4) += sleep44xx.o
obj-$(CONFIG_SOC_OMAP5) += omap-mpuss-lowpower.o sleep44xx.o
2009-05-28 21:56:16 +04:00
obj-$(CONFIG_PM_DEBUG) += pm-debug.o
2012-04-24 10:08:50 +04:00
2012-04-25 15:13:17 +04:00
obj-$(CONFIG_POWER_AVS_OMAP) += sr_device.o
2012-09-12 05:09:13 +04:00
obj-$(CONFIG_POWER_AVS_OMAP_CLASS3) += smartreflex-class3.o
2010-02-12 23:26:46 +03:00
AFLAGS_sleep24xx.o := -Wa,-march= armv6
2011-04-26 13:24:50 +04:00
AFLAGS_sleep34xx.o := -Wa,-march= armv7-a$( plus_sec)
2010-02-12 23:26:46 +03:00
2009-11-06 06:06:01 +03:00
i f e q ( $( CONFIG_PM_VERBOSE ) , y )
CFLAGS_pm_bus.o += -DDEBUG
e n d i f
2008-10-06 16:49:15 +04:00
e n d i f
2006-04-02 20:46:27 +04:00
2012-05-10 14:02:57 +04:00
i f e q ( $( CONFIG_CPU_IDLE ) , y )
2012-09-12 05:09:13 +04:00
obj-$(CONFIG_ARCH_OMAP3) += cpuidle34xx.o
obj-$(CONFIG_ARCH_OMAP4) += cpuidle44xx.o
2012-05-10 14:02:57 +04:00
e n d i f
2009-09-03 21:14:02 +04:00
# PRCM
2012-09-12 05:09:15 +04:00
obj-y += prcm.o prm_common.o
obj-$(CONFIG_ARCH_OMAP2) += cm2xxx_3xxx.o prm2xxx_3xxx.o
obj-$(CONFIG_ARCH_OMAP3) += cm2xxx_3xxx.o prm2xxx_3xxx.o
obj-$(CONFIG_ARCH_OMAP3) += vc3xxx_data.o vp3xxx_data.o
obj-$(CONFIG_SOC_AM33XX) += prm33xx.o cm33xx.o
omap-prcm-4-5-common = cminst44xx.o cm44xx.o prm44xx.o \
2012-06-05 14:51:32 +04:00
prcm_mpu44xx.o prminst44xx.o \
2012-09-12 05:09:14 +04:00
vc44xx_data.o vp44xx_data.o \
prm44xx.o
2012-09-12 05:09:15 +04:00
obj-$(CONFIG_ARCH_OMAP4) += $( omap-prcm-4-5-common)
2012-06-05 14:51:32 +04:00
obj-$(CONFIG_SOC_OMAP5) += $( omap-prcm-4-5-common)
2011-03-11 08:17:45 +03:00
# OMAP voltage domains
2012-09-12 05:09:15 +04:00
obj-y += voltage.o vc.o vp.o
2012-04-28 18:27:32 +04:00
obj-$(CONFIG_ARCH_OMAP2) += voltagedomains2xxx_data.o
obj-$(CONFIG_ARCH_OMAP3) += voltagedomains3xxx_data.o
obj-$(CONFIG_ARCH_OMAP4) += voltagedomains44xx_data.o
2012-09-12 05:09:13 +04:00
obj-$(CONFIG_SOC_AM33XX) += voltagedomains33xx_data.o
2010-12-22 06:01:17 +03:00
# OMAP powerdomain framework
2012-09-12 05:09:15 +04:00
obj-y += powerdomain.o powerdomain-common.o
2012-04-28 18:27:32 +04:00
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) += powerdomain2xxx_3xxx.o
obj-$(CONFIG_ARCH_OMAP3) += powerdomains3xxx_data.o
obj-$(CONFIG_ARCH_OMAP3) += powerdomains2xxx_3xxx_data.o
obj-$(CONFIG_ARCH_OMAP4) += powerdomain44xx.o
obj-$(CONFIG_ARCH_OMAP4) += powerdomains44xx_data.o
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 10:47:27 +04:00
obj-$(CONFIG_SOC_AM33XX) += powerdomain33xx.o
obj-$(CONFIG_SOC_AM33XX) += powerdomains33xx_data.o
2012-06-05 14:51:32 +04:00
obj-$(CONFIG_SOC_OMAP5) += powerdomain44xx.o
2009-09-03 21:14:02 +04:00
2010-12-22 06:01:20 +03:00
# PRCM clockdomain control
2012-09-12 05:09:15 +04:00
obj-y += clockdomain.o
2012-04-28 18:27:32 +04:00
obj-$(CONFIG_ARCH_OMAP2) += clockdomain2xxx_3xxx.o
obj-$(CONFIG_ARCH_OMAP2) += clockdomains2xxx_3xxx_data.o
2011-09-15 02:01:21 +04:00
obj-$(CONFIG_SOC_OMAP2420) += clockdomains2420_data.o
obj-$(CONFIG_SOC_OMAP2430) += clockdomains2430_data.o
2012-04-28 18:27:32 +04:00
obj-$(CONFIG_ARCH_OMAP3) += clockdomain2xxx_3xxx.o
obj-$(CONFIG_ARCH_OMAP3) += clockdomains2xxx_3xxx_data.o
obj-$(CONFIG_ARCH_OMAP3) += clockdomains3xxx_data.o
obj-$(CONFIG_ARCH_OMAP4) += clockdomain44xx.o
obj-$(CONFIG_ARCH_OMAP4) += clockdomains44xx_data.o
2012-06-18 10:47:27 +04:00
obj-$(CONFIG_SOC_AM33XX) += clockdomain33xx.o
obj-$(CONFIG_SOC_AM33XX) += clockdomains33xx_data.o
2012-06-05 14:51:32 +04:00
obj-$(CONFIG_SOC_OMAP5) += clockdomain44xx.o
2011-02-26 01:39:28 +03:00
2008-03-18 15:41:40 +03:00
# Clock framework
2012-09-12 05:09:14 +04:00
obj-y += clock.o clock_common_data.o \
clkt_dpll.o clkt_clksel.o
obj-$(CONFIG_ARCH_OMAP2) += clock2xxx.o
obj-$(CONFIG_ARCH_OMAP2) += clkt2xxx_dpllcore.o clkt2xxx_sys.o
2012-04-28 18:27:32 +04:00
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 03:39:40 +03:00
obj-$(CONFIG_SOC_OMAP2420) += clock2420_data.o
obj-$(CONFIG_SOC_OMAP2430) += clock2430.o clock2430_data.o
2012-09-12 05:09:14 +04:00
obj-$(CONFIG_ARCH_OMAP3) += clock3xxx.o
2012-04-28 18:27:32 +04:00
obj-$(CONFIG_ARCH_OMAP3) += clock34xx.o clkt34xx_dpll3m2.o
2012-09-12 05:09:14 +04:00
obj-$(CONFIG_ARCH_OMAP3) += clock3517.o clock36xx.o clkt_iclk.o
2012-04-28 18:27:32 +04:00
obj-$(CONFIG_ARCH_OMAP3) += dpll3xxx.o clock3xxx_data.o
2012-09-12 05:09:14 +04:00
obj-$(CONFIG_ARCH_OMAP4) += clock44xx_data.o
2012-04-28 18:27:32 +04:00
obj-$(CONFIG_ARCH_OMAP4) += dpll3xxx.o dpll44xx.o
2012-09-12 05:09:14 +04:00
obj-$(CONFIG_SOC_AM33XX) += dpll3xxx.o clock33xx_data.o
2012-06-05 14:51:32 +04:00
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 08:09:20 +03:00
# OMAP2 clock rate set data (old "OPP" data)
2011-01-28 03:39:40 +03:00
obj-$(CONFIG_SOC_OMAP2420) += opp2420_data.o
obj-$(CONFIG_SOC_OMAP2430) += opp2430_data.o
2008-03-18 15:41:40 +03:00
2010-02-23 08:09:32 +03:00
# hwmod data
2012-09-12 05:09:13 +04:00
obj-y += omap_hwmod_common_data.o
2012-04-28 18:27:32 +04: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
2012-07-25 23:51:13 +04:00
obj-$(CONFIG_SOC_AM33XX) += omap_hwmod_33xx_data.o
2010-05-12 19:54:36 +04:00
obj-$(CONFIG_ARCH_OMAP4) += omap_hwmod_44xx_data.o
2008-03-18 15:41:40 +03:00
2009-12-01 16:03:31 +03: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 08:09:20 +03:00
obj-$(CONFIG_OMAP3_EMU) += emu.o
2012-09-24 03:28:29 +04:00
obj-$(CONFIG_HW_PERF_EVENTS) += pmu.o
2009-12-01 16:03:31 +03:00
2009-11-22 21:11:17 +03:00
obj-$(CONFIG_OMAP_MBOX_FWK) += mailbox_mach.o
mailbox_mach-objs := mailbox.o
2010-05-24 10:35:11 +04:00
obj-$(CONFIG_OMAP_IOMMU) += iommu2.o
iommu-$(CONFIG_OMAP_IOMMU) := omap-iommu.o
obj-y += $( iommu-m) $( iommu-y)
2009-01-28 22:32:09 +03:00
2010-10-04 20:09:14 +04:00
i f n e q ( $( CONFIG_TIDSPBRIDGE ) , )
obj-y += dsp.o
e n d i f
2012-05-09 03:23:33 +04:00
# OMAP2420 MSDI controller integration support ("MMC")
obj-$(CONFIG_SOC_OMAP2420) += msdi.o
2012-05-24 00:08:10 +04:00
i f n e q ( $( CONFIG_DRM_OMAP ) , )
obj-y += drm.o
e n d i f
2005-11-10 17:26:51 +03:00
# Specific board support
obj-$(CONFIG_MACH_OMAP_GENERIC) += board-generic.o
obj-$(CONFIG_MACH_OMAP_H4) += board-h4.o
2011-08-23 10:57:23 +04:00
obj-$(CONFIG_MACH_OMAP_2430SDP) += board-2430sdp.o
2006-04-02 20:46:27 +04:00
obj-$(CONFIG_MACH_OMAP_APOLLON) += board-apollon.o
2011-08-23 10:57:23 +04:00
obj-$(CONFIG_MACH_OMAP3_BEAGLE) += board-omap3beagle.o
2012-09-12 05:09:13 +04:00
obj-$(CONFIG_MACH_DEVKIT8000) += board-devkit8000.o
2011-08-23 10:57:23 +04:00
obj-$(CONFIG_MACH_OMAP_LDP) += board-ldp.o
2012-09-12 05:09:13 +04:00
obj-$(CONFIG_MACH_OMAP3530_LV_SOM) += board-omap3logic.o
obj-$(CONFIG_MACH_OMAP3_TORPEDO) += board-omap3logic.o
2011-08-23 10:57:23 +04:00
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 21:51:38 +04:00
obj-$(CONFIG_MACH_NOKIA_N8X0) += board-n8x0.o
2012-04-28 18:27:32 +04: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 10:57:23 +04:00
obj-$(CONFIG_MACH_CM_T35) += board-cm-t35.o
2010-09-21 20:03:09 +04:00
obj-$(CONFIG_MACH_CM_T3517) += board-cm-t3517.o
2011-08-23 10:57:23 +04:00
obj-$(CONFIG_MACH_IGEP0020) += board-igep0020.o
2012-08-17 20:03:43 +04:00
obj-$(CONFIG_MACH_TOUCHBOOK) += board-omap3touchbook.o
2011-11-02 07:11:00 +04:00
obj-$(CONFIG_MACH_OMAP_4430SDP) += board-4430sdp.o
obj-$(CONFIG_MACH_OMAP4_PANDA) += board-omap4panda.o
2011-08-23 10:57:23 +04:00
2011-11-02 07:11:00 +04:00
obj-$(CONFIG_MACH_PCM049) += board-omap4pcm049.o
2009-03-31 01:58:31 +04:00
2011-07-10 13:22:20 +04:00
obj-$(CONFIG_MACH_OMAP3517EVM) += board-am3517evm.o
2009-11-19 05:41:09 +03:00
2010-11-17 01:26:58 +03:00
obj-$(CONFIG_MACH_CRANEBOARD) += board-am3517crane.o
2011-08-23 10:57:23 +04:00
obj-$(CONFIG_MACH_SBC3530) += board-omap3stalker.o
2011-02-15 20:36:08 +03:00
obj-$(CONFIG_MACH_TI8168EVM) += board-ti8168evm.o
2011-12-13 22:48:55 +04:00
obj-$(CONFIG_MACH_TI8148EVM) += board-ti8168evm.o
2011-08-23 10:57:23 +04:00
2009-03-24 04:34:06 +03:00
# Platform specific device init code
2011-08-23 10:57:23 +04: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 04:34:06 +03:00
obj-y += usb-musb.o
2011-07-10 13:22:20 +04:00
obj-y += omap_phy_internal.o
2009-08-28 21:51:37 +04:00
obj-$(CONFIG_MACH_OMAP2_TUSB6010) += usb-tusb6010.o
2011-03-01 17:38:15 +03:00
obj-y += usb-host.o
2009-05-29 00:23:52 +04:00
onenand-$(CONFIG_MTD_ONENAND_OMAP2) := gpmc-onenand.o
obj-y += $( onenand-m) $( onenand-y)
2009-05-29 00:23:52 +04:00
2010-02-15 21:03:33 +03:00
nand-$(CONFIG_MTD_NAND_OMAP2) := gpmc-nand.o
obj-y += $( nand-m) $( nand-y)
2009-05-29 00:23:52 +04:00
smc91x-$(CONFIG_SMC91X) := gpmc-smc91x.o
obj-y += $( smc91x-m) $( smc91x-y)
2010-09-27 20:05:49 +04:00
smsc911x-$(CONFIG_SMSC911X) := gpmc-smsc911x.o
obj-y += $( smsc911x-m) $( smsc911x-y)
2012-03-06 04:11:02 +04:00
i f n e q ( $( CONFIG_HWSPINLOCK_OMAP ) , )
obj-y += hwspinlock.o
e n d i f
2011-01-24 09:21:54 +03:00
2012-03-05 23:08:36 +04:00
emac-$(CONFIG_TI_DAVINCI_EMAC) := am35xx-emac.o
obj-y += $( emac-m) $( emac-y)
2012-11-05 17:14:17 +04:00
obj-y += common-board-devices.o twl-common.o dss-common.o