Texas Instruments DM365, User Manual

Page: 18 / 131

Introduction
1-6
framework, and if the resource is available, the client grants the algorithm
logical IRES resource handles representing the allotted resources. Each
handle provides the algorithm with access to the resource as defined by the
concrete IRES resource interface.
IRES interface definition and function-calling sequence is depicted in the
following figure. For more details, see
Using IRES and RMAN Framework
Components for C64x+ (literature number SPRAAI5).
Figure 1-3. IRES Interface Definition and Function-calling Sequence.
In DM365/DM368, FC manages multiple resources for smooth interaction with
other algorithms and application. The resources and the utilities provided by
FC are listed in this section.
1.2.3.2 HDVICP
The IRES HDVICP Resource Interface, IRES_HDVICP, allows algorithms
to request and receive handles representing Hardware Accelerator
resource, HDVICP, on supported hardware platforms. Algorithms can
request and acquire one of the co-processors using a single IRES request
descriptor. IRES_HDVICP is an example of a very simple resource type
definition, which operates at the granularity of the entire processor and
does not publish any details about the resource that is being acquired other
than the ‘id’ of the processor. It leaves it up to the algorithm to manage
internals of the resource based on the ID.
1.2.3.3 EDMA3
The IRES EDMA3 Resource Interface, IRES_EDMA3CHAN, allows
algorithms to request and receive handles representing EDMA3 resources
associated with a single EDMA3 channel. This is a very low-level resource
definition.