2010-04-30 22:06:50 -07:00
obj-y += io.o idle.o timer.o dma.o
2010-03-03 08:54:11 -08:00
obj-y += acpuclock-arm11.o
2007-11-26 04:11:43 -08:00
2010-04-30 22:06:50 -07:00
i f d e f C O N F I G _ M S M _ V I C
obj-y += irq-vic.o
e l s e
obj-y += irq.o
e n d i f
2010-08-17 20:04:19 -07:00
obj-$(CONFIG_ARCH_MSM8X60) += clock-dummy.o
2010-04-21 16:20:27 -07:00
obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o
obj-$(CONFIG_MSM_PROC_COMM) += clock.o
2010-05-06 13:54:17 -07:00
obj-$(CONFIG_ARCH_QSD8X50) += sirc.o
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
2007-11-26 04:12:13 -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-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
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_MSM7X30) += gpiomux-7x30.o gpiomux-v1.o gpiomux.o
obj-$(CONFIG_ARCH_QSD8X50) += gpiomux-8x50.o gpiomux-v1.o gpiomux.o
obj-$(CONFIG_ARCH_MSM8X60) += gpiomux-8x60.o gpiomux-v2.o gpiomux.o
2010-09-10 15:03:36 -07:00
i f n d e f C O N F I G _ M S M _ V 2 _ T L M M
obj-y += gpio.o
e n d i f