Table of Contents
Advertisement
4.2
Step-by-Step procedure for porting
4.2.1
edma3_<PLATFORM_NAME>_cfg.c:
This section provides illustrative description on how to port the
EDMA3 Resource Manager to the selected platform and the OS.
EDMA3_RM_GblConfigParams is the initialization structure which
is used to specify the EDMA3 Hardware specific global settings,
specific to the SoC. For e.g. number of DMA/QDMA channels,
number of PaRAM sets, TCCs, event queues, transfer controllers,
base addresses of CC global registers and TC registers, interrupt
number for EDMA3 transfer completion, CC error, event queues'
priority, watermark
information is SoC specific and could be provided by the user at
run-time also while creating the EDMA3 Resource Manager
object. In case user doesn't provide it, this information will be
taken from the configuration file, in case it is available for the
specific SoC.
Similarly,
EDMA3_RM_InstanceInitConfig
structure which is used to specify the EDMA3 Resource Manager
Region
specific
settings.
channels, PaRAM sets, TCCs) owned and reserved by this EDMA3
driver instance. This configuration information is shadow region
(or master) specific and could be provided by the user at run-
time while creating the EDMA3 Resource Manager instance. In
case user doesn't provide it, this information will be taken from
the configuration file, in case it is available for the specific SoC
for the specific shadow region.
To summarize, this file contains the global and region specific
configuration information for EDMA3 for the specific platform.
User can create this file by adding the desired information for the
new SoC, or he/she can provide this info at init-time.
User can find the sample configuration files for different platforms
at:
"edma3_lld_<VERSION_NUMBER>\packages\ti\sdo\edma3\rm\sr
c\configs". On the same lines, user can create different
configuration file for another platform.
threshold
level
etc.
For
e.g.
resources
This
configuration
is
the
initialization
(DMA/QDMA
34
Advertisement
Table of Contents
