(dv)usingedmaandacpy.pptVIP

DSPx m Linux Embedded System Design Workshop Outline How To Move Blocks of Memory? Outline Multiple DMA’s : EDMA3 and QDMA Multiple DMA’s : Master Periphs C64x+ IDMA Outline DMA : Direct Memory Access How Much to Move? Outline EDMA Example : Simple (Horizontal Line) EDMA Example : Simple (Horizontal Line) EDMA Example : Indexing (Vertical Line) EDMA Example : Block Transfer EDMA Example : Block Transfer (less efficient) EDMA Example : Block Transfer (more efficient) Outline ACPY3 Method Chronology ACPY3 DMA Transfer Abstaction ACPY3_configure TransferType : 1D / 2D ACPY3_configure Example ACPY3_configure Example Code ACPY3 Interface ACPY3_fastConfigure32b, 16b ACPY3_activate, ACPY3_deactivate ACPY3_start ACPY3_wait, _waitLinked ACPY3_complete, _completeLinked ACPY3_setFinal Outline Outline Event – Transfer – Action Event – Transfer – Action Outline Sequential DMA Transfers Outline ACPY3_configure Example ACPY3 Adv. Code Example ACPY3 Adv. Code Example Outline EDMA3 : Shared Resources Outline Solution to Limited Resources DMAN3 / IDMA3 / ACPY3 Interaction DMAN3 / IDMA3 / ACPY3 Interaction iDMA3 : Revisiting the Lifecycle of an Algo Instance Memory / DMA Resource Mgmt Comparison Outline Coding iDMA3 Functions (Algo Author) Outline DMAN3 Concepts DMAN3 Setup : server.cfg DMAN3 Framework Calling DMAN3 (Application Author) EDMA3 Architecture EDMA : Adding Synchronization to DMA ACPY3_configure Outline Note : ACPY3_wait is a spin loop (not a block) – enforces resource holding – don’t want to allow some other SG member to run and override currently in use resources… It isn’t necessary to step through each API call here, the important point is that the IALG API provide a means to instantiate an algorithm instance by providing a handshaking mechanism by which a framework (i.e. the CODEC engine) can query the algorithm for its memory needs and then grant them. The CODEC engine framework instantiates algorithms (using the xxx_create method), therefore xDAIS is an int