The DPAA2 CMDIF is an implementation of the rawdev API, that provides communication between the GPP and AIOP (Firmware). This is achieved via using the DPCI devices exposed by MC for GPP <–> AIOP interaction.
More information can be found at NXP Official Website.
The DPAA2 CMDIF 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_CMDIF_RAWDEV (default y)
Toggle compilation of the lrte_pmd_dpaa2_cmdif driver.
For enabling logs, use the following EAL parameter:
./your_cmdif_application <EAL args> --log-level=pmd.raw.dpaa2.cmdif,<level>
Using pmd.raw.dpaa2.cmdif as log matching criteria, all Event PMD logs can be enabled which are lower than logging level.
To compile the DPAA2 CMDIF PMD for Linux arm64 gcc target, run the following make command:
cd <DPDK-source-directory>
make config T=arm64-dpaa-linux-gcc install
The DPAA2 CMDIF is exposed as a vdev device which consists of dpci devices. On EAL initialization, dpci devices will be probed and then vdev device can be created from the application code by
Example:
./your_cmdif_application <EAL args> --vdev="dpaa2_dpci"
DPAA2 drivers for DPDK can only work on NXP SoCs as listed in the Supported DPAA2 SoCs.