1 .. SPDX-License-Identifier: BSD-3-Clause
7 The DPAA2 QDMA is an implementation of the rawdev API, that provide means
8 to initiate a DMA transaction from CPU. The initiated DMA is performed
9 without CPU being involved in the actual DMA transaction. This is achieved
10 via using the DPDMAI device exposed by MC.
12 More information can be found at `NXP Official Website
13 <http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/qoriq-arm-processors:QORIQ-ARM>`_.
18 The DPAA2 QDMA implements following features in the rawdev API;
20 - Supports issuing DMA of data within memory without hogging CPU while
21 performing DMA operation.
22 - Supports configuring to optionally get status of the DMA translation on
23 per DMA operation basis.
36 See :doc:`../platform/dpaa2` for setup information
38 Currently supported by DPDK:
41 - MC Firmware version **10.18.0** and higher.
42 - Supported architectures: **arm64 LE**.
44 - Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment.
48 Some part of fslmc bus code (mc flib - object library) routines are
49 dual licensed (BSD & GPLv2).
51 Pre-Installation Configuration
52 ------------------------------
57 The following options can be modified in the ``config`` file.
59 - ``CONFIG_RTE_LIBRTE_PMD_DPAA2_QDMA_RAWDEV`` (default ``y``)
61 Toggle compilation of the ``lrte_pmd_dpaa2_qdma`` driver.
66 For enabling logs, use the following EAL parameter:
68 .. code-block:: console
70 ./your_qdma_application <EAL args> --log-level=pmd.raw.dpaa2.qdma,<level>
72 Using ``pmd.raw.dpaa2.qdma`` as log matching criteria, all Event PMD logs can be
73 enabled which are lower than logging ``level``.
78 To compile the DPAA2 QDMA PMD for Linux arm64 gcc target, run the
79 following ``make`` command:
81 .. code-block:: console
83 cd <DPDK-source-directory>
84 make config T=arm64-dpaa-linux-gcc install
89 The DPAA2 QDMA is exposed as a vdev device which consists of dpdmai devices.
90 On EAL initialization, dpdmai devices will be probed and populated into the
91 rawdevices. The rawdev ID of the device can be obtained using
93 * Invoking ``rte_rawdev_get_dev_id("dpdmai.x")`` from the application
94 where x is the object ID of the DPDMAI object created by MC. Use can
95 use this index for further rawdev function calls.
100 DPAA2 drivers for DPDK can only work on NXP SoCs as listed in the
101 ``Supported DPAA2 SoCs``.