summaryrefslogtreecommitdiff
path: root/drivers/dma/Makefile
diff options
context:
space:
mode:
authorKhoronzhuk, Ivan <ivan.khoronzhuk@ti.com>2014-10-22 18:47:56 +0400
committerTom Rini <trini@ti.com>2014-10-23 19:27:29 +0400
commite165b1d34cd91cb42b0614792aa88e0677944ee7 (patch)
treeda7da2e4c75c78788e2fc485e22807f19169953b /drivers/dma/Makefile
parent00b821f16e65d1242b026dcc9834ddeab2fffcab (diff)
downloadu-boot-e165b1d34cd91cb42b0614792aa88e0677944ee7.tar.xz
dma: ti-edma3: introduce edma3 driver
The EDMA3 controller’s primary purpose is to service data transfers that you program between two memory-mapped slave endpoints on the device. Typical usage includes, but is not limited to the following: - Servicing software-driven paging transfers (e.g., transfers from external memory, such as SDRAM to internal device memory, such as DSP L2 SRAM) - Servicing event-driven peripherals, such as a serial port - Performing sorting or sub-frame extraction of various data structures - Offloading data transfers from the main device DSP(s) - See the device-specific data manual for specific peripherals that are accessible via the EDMA3 controller Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Diffstat (limited to 'drivers/dma/Makefile')
-rw-r--r--drivers/dma/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/dma/Makefile b/drivers/dma/Makefile
index 15b0780b5d..4c8fcc2575 100644
--- a/drivers/dma/Makefile
+++ b/drivers/dma/Makefile
@@ -9,3 +9,4 @@ obj-$(CONFIG_FSLDMAFEC) += MCD_tasksInit.o MCD_dmaApi.o MCD_tasks.o
obj-$(CONFIG_APBH_DMA) += apbh_dma.o
obj-$(CONFIG_FSL_DMA) += fsl_dma.o
obj-$(CONFIG_TI_KSNAV) += keystone_nav.o keystone_nav_cfg.o
+obj-$(CONFIG_TI_EDMA3) += ti-edma3.o