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-02-24 00:41:52 +00:00
|
|
|
common.o gpio.o dma.o wd_timer.o display.o i2c.o
|
2009-05-25 18:26:47 +00:00
|
|
|
|
2010-12-21 22:30:55 +00:00
|
|
|
omap-2-3-common = irq.o sdrc.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)
|
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
|
|
|
|
|
2009-04-28 15:22:05 +00:00
|
|
|
# SMP support ONLY available for OMAP4
|
|
|
|
obj-$(CONFIG_SMP) += omap-smp.o omap-headsmp.o
|
2010-08-02 10:18:19 +00:00
|
|
|
obj-$(CONFIG_HOTPLUG_CPU) += omap-hotplug.o
|
2010-06-16 16:49:48 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += omap4-common.o omap-wakeupgen.o \
|
|
|
|
sleep44xx.o
|
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
|
2011-03-11 05:17:45 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += pm34xx.o sleep34xx.o \
|
2011-04-28 22:36:42 +00:00
|
|
|
cpuidle34xx.o
|
2011-08-16 12:01:40 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o omap-mpuss-lowpower.o \
|
|
|
|
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
|
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
|
2011-03-11 05:17:45 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += prcm.o cm2xxx_3xxx.o prm2xxx_3xxx.o \
|
|
|
|
vc3xxx_data.o vp3xxx_data.o
|
2010-12-21 22:30:55 +00:00
|
|
|
# XXX The presence of cm2xxx_3xxx.o on the line below is temporary and
|
|
|
|
# will be removed once the OMAP4 part of the codebase is converted to
|
|
|
|
# use OMAP4-specific PRCM functions.
|
OMAP4: PRCM: add OMAP4-specific accessor/mutator functions
In some ways, the OMAP4 PRCM register layout is quite different than
the OMAP2/3 PRCM register layout. For example, on OMAP2/3, from a
register layout point of view, all CM instances were located in the CM
subsystem, and all PRM instances were located in the PRM subsystem.
OMAP4 changes this. Now, for example, some CM instances, such as
WKUP_CM and EMU_CM, are located in the system PRM subsystem. And a
"local PRCM" exists for the MPU - this PRCM combines registers that
would normally appear in both CM and PRM instances, but uses its own
register layout which matches neither the OMAP2/3 PRCM layout nor the
OMAP4 PRCM layout.
To try to deal with this, introduce some new functions, omap4_cminst*
and omap4_prminst*. The former is to be used when writing to a CM
instance register (no matter what subsystem or hardware module it
exists in), and the latter, similarly, with PRM instance registers.
To determine which "PRCM partition" to write to, the functions take a
PRCM instance ID argument. Subsequent patches add these partition IDs
to the OMAP4 powerdomain and clockdomain definitions.
As far as I can see, there's really no good way to handle these types
of register access inconsistencies. This patch seemed like the least
bad approach.
Moving forward, the long-term goal is to remove all direct PRCM
register access from the PM code. PRCM register access should go
through layers such as the powerdomain and clockdomain code that can
hide the details of how to interact with the specific hardware
variant.
While here, rename cm4xxx.c to cm44xx.c to match the naming convention
of the other OMAP4 PRCM files.
Thanks to Santosh Shilimkar <santosh.shilimkar@ti.com>, Rajendra Nayak
<rnayak@ti.com>, and Benoît Cousson <b-cousson@ti.com> for some comments.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Benoît Cousson <b-cousson@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
2010-12-22 04:05:14 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += prcm.o cm2xxx_3xxx.o cminst44xx.o \
|
|
|
|
cm44xx.o prcm_mpu44xx.o \
|
2011-03-11 05:17:45 +00:00
|
|
|
prminst44xx.o vc44xx_data.o \
|
2011-12-16 21:36:58 +00:00
|
|
|
vp44xx_data.o prm44xx.o
|
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
|
2011-03-23 23:09:41 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += $(voltagedomain-common) \
|
|
|
|
voltagedomains2xxx_data.o
|
2011-03-11 05:17:45 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += $(voltagedomain-common) \
|
|
|
|
voltagedomains3xxx_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(voltagedomain-common) \
|
|
|
|
voltagedomains44xx_data.o
|
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
|
2010-12-22 03:01:18 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += $(powerdomain-common) \
|
2010-12-22 03:01:20 +00:00
|
|
|
powerdomain2xxx_3xxx.o \
|
|
|
|
powerdomains2xxx_data.o \
|
|
|
|
powerdomains2xxx_3xxx_data.o
|
2010-12-22 03:01:18 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += $(powerdomain-common) \
|
2010-12-22 03:01:20 +00:00
|
|
|
powerdomain2xxx_3xxx.o \
|
|
|
|
powerdomains3xxx_data.o \
|
|
|
|
powerdomains2xxx_3xxx_data.o
|
2010-12-22 03:01:18 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(powerdomain-common) \
|
2010-12-22 03:01:20 +00:00
|
|
|
powerdomain44xx.o \
|
|
|
|
powerdomains44xx_data.o
|
2009-09-03 17:14:02 +00:00
|
|
|
|
2010-12-22 03:01:20 +00:00
|
|
|
# PRCM clockdomain control
|
2012-04-19 19:33:49 +00:00
|
|
|
clockdomain-common += clockdomain.o \
|
|
|
|
clockdomains_common_data.o
|
|
|
|
obj-$(CONFIG_ARCH_OMAP2) += $(clockdomain-common) \
|
2011-02-25 23:06:47 +00:00
|
|
|
clockdomain2xxx_3xxx.o \
|
2010-12-22 03:01:20 +00:00
|
|
|
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-04-19 19:33:49 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += $(clockdomain-common) \
|
2011-02-25 23:06:47 +00:00
|
|
|
clockdomain2xxx_3xxx.o \
|
2011-09-14 22:01:21 +00:00
|
|
|
clockdomains2xxx_3xxx_data.o \
|
|
|
|
clockdomains3xxx_data.o
|
2012-04-19 19:33:49 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(clockdomain-common) \
|
2011-02-25 23:06:47 +00:00
|
|
|
clockdomain44xx.o \
|
2010-12-22 03:01:20 +00:00
|
|
|
clockdomains44xx_data.o
|
2011-02-25 22:39:28 +00:00
|
|
|
|
2008-03-18 12:41:40 +00:00
|
|
|
# Clock framework
|
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_ARCH_OMAP2) += $(clock-common) clock2xxx.o \
|
OMAP2 clock: split OMAP2420, OMAP2430 clock data into their own files
In preparation for multi-OMAP2 kernels, split
mach-omap2/clock2xxx_data.c into mach-omap2/clock2420_data.c and
mach-omap2/clock2430_data.c. 2430 uses a different device space
physical memory layout than past or future OMAPs, and we use a
different virtual memory layout as well, which causes trouble for
architecture-level code/data that tries to support both. We tried
using offsets from the virtual base last year, but those patches never
made it upstream; so after some discussion with Tony about the best
all-around approach, we'll just grit our teeth and duplicate the
structures. The maintenance advantages of a single kernel config that
can compile and boot on OMAP2, 3, and 4 platforms are simply too
compelling.
This approach does have some nice benefits beyond multi-OMAP 2 kernel
support. The runtime size of OMAP2420-specific and OMAP2430-specific
kernels is smaller, since unused clocks for the other OMAP2 chip will
no longer be compiled in. (At some point we will mark the clock data
__initdata and allocate it during registration, which will eliminate
the runtime memory advantage.) It also makes the clock trees slightly
easier to read, since 2420-specific and 2430-specific clocks are no
longer mixed together.
This patch also splits 2430-specific clock code into its own file,
mach-omap2/clock2430.c, which is only compiled in for 2430 builds -
mostly for organizational clarity.
While here, fix a bug in the OMAP2430 clock tree: "emul_ck" was
incorrectly marked as being 2420-only, when actually it is present on
both OMAP2420 and OMAP2430.
Thanks to Tony for some good discussions about how to approach this
problem.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Richard Woodruff <r-woodruff2@ti.com>
2010-02-23 05:09:22 +00:00
|
|
|
clkt2xxx_sys.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
|
|
|
clkt2xxx_dpllcore.o \
|
|
|
|
clkt2xxx_virt_prcm_set.o \
|
2011-02-25 22:49:53 +00:00
|
|
|
clkt2xxx_apll.o clkt2xxx_osc.o \
|
2011-02-25 22:39:28 +00:00
|
|
|
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
|
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_ARCH_OMAP3) += $(clock-common) clock3xxx.o \
|
|
|
|
clock34xx.o clkt34xx_dpll3m2.o \
|
|
|
|
clock3517.o clock36xx.o \
|
2011-02-25 22:39:28 +00:00
|
|
|
dpll3xxx.o clock3xxx_data.o \
|
|
|
|
clkt_iclk.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
|
|
|
obj-$(CONFIG_ARCH_OMAP4) += $(clock-common) clock44xx_data.o \
|
2011-02-25 22:49:01 +00:00
|
|
|
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
|
2011-07-10 01:14:07 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP2420) += omap_hwmod_2xxx_ipblock_data.o \
|
|
|
|
omap_hwmod_2xxx_3xxx_ipblock_data.o \
|
|
|
|
omap_hwmod_2xxx_interconnect_data.o \
|
2011-07-10 01:14:06 +00:00
|
|
|
omap_hwmod_2xxx_3xxx_interconnect_data.o \
|
|
|
|
omap_hwmod_2420_data.o
|
2011-07-10 01:14:07 +00:00
|
|
|
obj-$(CONFIG_SOC_OMAP2430) += omap_hwmod_2xxx_ipblock_data.o \
|
|
|
|
omap_hwmod_2xxx_3xxx_ipblock_data.o \
|
|
|
|
omap_hwmod_2xxx_interconnect_data.o \
|
2011-07-10 01:14:06 +00:00
|
|
|
omap_hwmod_2xxx_3xxx_interconnect_data.o \
|
|
|
|
omap_hwmod_2430_data.o
|
2011-07-10 01:14:07 +00:00
|
|
|
obj-$(CONFIG_ARCH_OMAP3) += omap_hwmod_2xxx_3xxx_ipblock_data.o \
|
|
|
|
omap_hwmod_2xxx_3xxx_interconnect_data.o \
|
2011-07-10 01:14:06 +00:00
|
|
|
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
|
|
|
|
|
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
|
2010-12-17 23:13:47 +00:00
|
|
|
obj-$(CONFIG_MACH_NOKIA_RM680) += board-rm680.o \
|
2011-08-23 06:57:23 +00:00
|
|
|
sdram-nokia.o
|
2009-03-24 01:38:17 +00:00
|
|
|
obj-$(CONFIG_MACH_NOKIA_RX51) += board-rx51.o \
|
2010-12-17 23:13:44 +00:00
|
|
|
sdram-nokia.o \
|
2009-03-24 01:38:17 +00:00
|
|
|
board-rx51-peripherals.o \
|
2011-08-23 06:57:23 +00:00
|
|
|
board-rx51-video.o
|
2010-11-08 06:56:14 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP_ZOOM2) += board-zoom.o \
|
2009-11-22 18:11:30 +00:00
|
|
|
board-zoom-peripherals.o \
|
2010-11-15 06:09:03 +00:00
|
|
|
board-zoom-display.o \
|
2009-05-28 21:04:04 +00:00
|
|
|
board-zoom-debugboard.o
|
2010-11-08 06:56:14 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP_ZOOM3) += board-zoom.o \
|
2009-11-22 18:11:32 +00:00
|
|
|
board-zoom-peripherals.o \
|
2010-11-15 06:09:03 +00:00
|
|
|
board-zoom-display.o \
|
2009-05-28 21:04:04 +00:00
|
|
|
board-zoom-debugboard.o
|
2009-11-19 02:41:08 +00:00
|
|
|
obj-$(CONFIG_MACH_OMAP_3630SDP) += board-3630sdp.o \
|
|
|
|
board-zoom-peripherals.o \
|
2011-08-23 06:57:23 +00:00
|
|
|
board-zoom-display.o
|
|
|
|
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)
|
|
|
|
|
|
|
|
|
2010-07-05 13:31:29 +00:00
|
|
|
usbfs-$(CONFIG_ARCH_OMAP_OTG) := usb-fs.o
|
|
|
|
obj-y += $(usbfs-m) $(usbfs-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
|