1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2018-2022 NXP
7 The DPAA2 QDMA is an implementation of the dmadev 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 dmadev 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.
24 - Supports statistics.
37 See :doc:`../platform/dpaa2` for setup information
39 - Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment.
43 Some part of fslmc bus code (mc flib - object library) routines are
44 dual licensed (BSD & GPLv2).
50 For enabling logs, use the following EAL parameter:
52 .. code-block:: console
54 ./your_qdma_application <EAL args> --log-level=pmd.dma.dpaa2.qdma,<level>
56 Using ``pmd.dma.dpaa2.qdma`` as log matching criteria, all Event PMD logs can be
57 enabled which are lower than logging ``level``.
63 The DPAA2 QDMA is exposed as a dma device which consists of dpdmai devices.
64 On EAL initialization, dpdmai devices will be probed and populated into the
65 dmadevices. The dmadev ID of the device can be obtained using
67 * Invoking ``rte_dma_get_dev_id_by_name("dpdmai.x")`` from the application
68 where x is the object ID of the DPDMAI object created by MC. Use can
69 use this index for further rawdev function calls.
74 DPAA2 drivers for DPDK can only work on NXP SoCs as listed in the
75 ``Supported DPAA2 SoCs``.