diff options
| author | Khoronzhuk, Ivan <ivan.khoronzhuk@ti.com> | 2014-10-22 17:47:56 +0300 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2014-10-23 11:27:29 -0400 |
| commit | e165b1d34cd91cb42b0614792aa88e0677944ee7 (patch) | |
| tree | da7da2e4c75c78788e2fc485e22807f19169953b /arch/arm/include/asm/arch-mx35 | |
| parent | 00b821f16e65d1242b026dcc9834ddeab2fffcab (diff) | |
| download | u-boot-imx-e165b1d34cd91cb42b0614792aa88e0677944ee7.zip u-boot-imx-e165b1d34cd91cb42b0614792aa88e0677944ee7.tar.gz u-boot-imx-e165b1d34cd91cb42b0614792aa88e0677944ee7.tar.bz2 | |
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 'arch/arm/include/asm/arch-mx35')
0 files changed, 0 insertions, 0 deletions