1 .. SPDX-License-Identifier: BSD-3-Clause
5 NXP DPAA2 Eventdev Driver
6 =========================
8 The dpaa2 eventdev is an implementation of the eventdev API, that provides a
9 wide range of the eventdev features. The eventdev relies on a dpaa2 hw to
10 perform event scheduling.
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 EVENTDEV implements many features in the eventdev API;
20 - Hardware based event scheduler
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 The dpaa2 eventdev is exposed as a vdev device which consists of a set of dpcon
51 devices and dpci devices. On EAL initialization, dpcon and dpci devices will be
52 probed and then vdev device can be created from the application code by
54 * Invoking ``rte_vdev_init("event_dpaa2")`` from the application
56 * Using ``--vdev="event_dpaa2"`` in the EAL options, which will call
57 rte_vdev_init() internally
61 .. code-block:: console
63 ./your_eventdev_application --vdev="event_dpaa2"
68 For enabling logs, use the following EAL parameter:
70 .. code-block:: console
72 ./your_eventdev_application <EAL args> --log-level=pmd.event.dpaa2,<level>
74 Using ``eventdev.dpaa2`` as log matching criteria, all Event PMD logs can be
75 enabled which are lower than logging ``level``.
83 DPAA2 drivers for DPDK can only work on NXP SoCs as listed in the
84 ``Supported DPAA2 SoCs``.
89 DPAA2 EVENTDEV can support only one eventport per core.