The DPAA2 QDMA is an implementation of the rawdev API, that provide means to initiate a DMA transaction from CPU. The initiated DMA is performed without CPU being involved in the actual DMA transaction. This is achieved via using the DPDMAI device exposed by MC.
More information can be found at NXP Official Website.
The DPAA2 QDMA implements following features in the rawdev API;
See NXP QorIQ DPAA2 Board Support Package for setup information
Currently supported by DPDK:
Note
Some part of fslmc bus code (mc flib - object library) routines are dual licensed (BSD & GPLv2).
The following options can be modified in the config file.
CONFIG_RTE_LIBRTE_PMD_DPAA2_QDMA_RAWDEV (default y)
Toggle compilation of the lrte_pmd_dpaa2_qdma driver.
For enabling logs, use the following EAL parameter:
./your_qdma_application <EAL args> --log-level=pmd.raw.dpaa2.qdma,<level>
Using pmd.raw.dpaa2.qdma as log matching criteria, all Event PMD logs can be enabled which are lower than logging level.
To compile the DPAA2 QDMA PMD for Linux arm64 gcc target, run the following make command:
cd <DPDK-source-directory>
make config T=arm64-dpaa2-linuxapp-gcc install
The DPAA2 QDMA is exposed as a vdev device which consists of dpdmai devices. On EAL initialization, dpdmai devices will be probed and populated into the rawdevices. The rawdev ID of the device can be obtained using
DPAA2 drivers for DPDK can only work on NXP SoCs as listed in the Supported DPAA2 SoCs.