2012-08-22 15:55:45 -07:00
obj-y += io.o timer.o
2011-02-23 09:37:41 -08:00
obj-y += clock.o
2011-01-26 16:20:54 -08:00
obj-$(CONFIG_DEBUG_FS) += clock-debug.o
2007-11-26 04:11:43 -08:00
2010-12-09 19:16:13 -08:00
obj-$(CONFIG_MSM_VIC) += irq-vic.o
2011-06-02 03:20:08 +03:00
obj-$(CONFIG_MSM_IOMMU) += devices-iommu.o
2010-04-30 22:06:50 -07:00
2012-09-06 19:48:40 -07:00
obj-$(CONFIG_ARCH_MSM7X00A) += dma.o irq.o
2010-12-09 19:16:13 -08:00
obj-$(CONFIG_ARCH_MSM7X30) += dma.o
obj-$(CONFIG_ARCH_QSD8X50) += dma.o sirc.o
2010-04-21 16:20:27 -07:00
obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o
2010-12-09 19:16:13 -08:00
2009-07-01 17:58:37 -07:00
obj-$(CONFIG_MSM_SMD) += smd.o smd_debug.o
2009-11-15 18:16:43 -08:00
obj-$(CONFIG_MSM_SMD) += last_radio_log.o
2010-10-14 19:19:21 -07:00
obj-$(CONFIG_MSM_SCM) += scm.o scm-boot.o
2007-11-26 04:12:13 -08:00
2011-11-08 13:07:36 +00:00
CFLAGS_scm.o := $( call as-instr,.arch_extension sec,-DREQUIRES_SEC= 1)
2010-12-02 12:11:27 -08:00
obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o
2010-11-30 13:06:36 -08:00
obj-$(CONFIG_SMP) += headsmp.o platsmp.o
2010-12-02 12:11:27 -08:00
2010-03-30 16:11:57 -07:00
obj-$(CONFIG_MACH_TROUT) += board-trout.o board-trout-gpio.o board-trout-mmc.o devices-msm7x00.o
2010-12-13 14:35:11 -08:00
obj-$(CONFIG_MACH_TROUT) += board-trout.o board-trout-gpio.o board-trout-mmc.o board-trout-panel.o devices-msm7x00.o
2010-04-30 21:21:24 -07:00
obj-$(CONFIG_MACH_HALIBUT) += board-halibut.o devices-msm7x00.o
2010-05-06 12:44:57 -07:00
obj-$(CONFIG_ARCH_MSM7X30) += board-msm7x30.o devices-msm7x30.o
2010-05-06 13:54:17 -07:00
obj-$(CONFIG_ARCH_QSD8X50) += board-qsd8x50.o devices-qsd8x50.o
2012-09-05 12:28:56 -07:00
obj-$(CONFIG_ARCH_MSM8X60) += board-dt-8660.o
2012-09-05 12:28:58 -07:00
obj-$(CONFIG_ARCH_MSM8960) += board-dt-8960.o
2010-05-06 13:54:17 -07:00
2011-01-10 11:00:30 -08:00
obj-$(CONFIG_ARCH_MSM7X30) += gpiomux-v1.o gpiomux.o
msm: add gpiomux api for gpio multiplex & configuration.
Add the 'gpiomux' api, which addresses the following shortcomings
of existing tlmm api:
- gpio power-collapse, which is managed by a peripheral processor on
other targets, must be managed by the application processor on the 8x60.
- The enable/disable flag of the legacy gpio_tlmm_config api
is not applicable on the 8x60, and causes confusion.
- The gpio 'direction' bits are meaningless for all func_sel
configurations except for generic-gpio mode (func_sel 0), in which
case the gpio_direction_* functions should be used. Having these
bits in the tlmm api leads to confusion and misuse of the gpiolib
api, and they have been removed in gpiomux.
- The functional api of the legacy system ran contrary to the typical
use-case, which is a single massive configuration at boot. Rather
than forcing hundreds of 'config' function calls, the new api
allows data to be configured with a single table.
gpiomux_get and gpiomux_put are meant to be called automatically
when gpio_request and gpio_free are called, giving automatic
gpiomux/tlmm control to those drivers/lines with simple
power profiles - in the simplest cases, an entry in the gpiomux table
and the correct usage of gpiolib is all that is required to get proper
gpio power control.
Signed-off-by: Gregory Bean <gbean@codeaurora.org>
Signed-off-by: Daniel Walker <dwalker@codeaurora.org>
2010-08-28 10:05:44 -07:00
obj-$(CONFIG_ARCH_QSD8X50) += gpiomux-8x50.o gpiomux-v1.o gpiomux.o
obj-$(CONFIG_ARCH_MSM8X60) += gpiomux-8x60.o gpiomux-v2.o gpiomux.o