-----Original Message----- > Date: Thu, 25 May 2017 23:37:51 +0530 > From: Nipun Gupta <[email protected]> > To: [email protected] > CC: [email protected], [email protected], > [email protected], [email protected], > [email protected], [email protected], Nipun Gupta > <[email protected]> > Subject: [PATCH 20/20] doc: add NXP DPAA2 EVENTDEV details > X-Mailer: git-send-email 1.9.1 > > Signed-off-by: Nipun Gupta <[email protected]> > --- > MAINTAINERS | 1 + > doc/guides/eventdevs/dpaa2.rst | 157 > +++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 158 insertions(+) > create mode 100644 doc/guides/eventdevs/dpaa2.rst > > diff --git a/MAINTAINERS b/MAINTAINERS > index 45e284e..9c9095b 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -584,6 +584,7 @@ NXP DPAA2 Eventdev PMD > M: Hemant Agrawal <[email protected]> > M: Nipun Gupta <[email protected]> > F: drivers/event/dpaa2/ > +F: doc/guides/eventdevs/dpaa2.rst > > Packet processing > ----------------- > + > +To compile the DPAA2 EVENTDEV PMD for Linux arm64 gcc target, run the > +following ``make`` command: > + > +.. code-block:: console > + > + cd <DPDK-source-directory> > + make config T=arm64-dpaa2-linuxapp-gcc install
It nice to mention your PMD driver vdev name in the document. > + > +Limitations > +----------- > + > +Platform Requirement > +~~~~~~~~~~~~~~~~~~~~ > + > +DPAA2 drivers for DPDK can only work on NXP SoCs as listed in the > +``Supported DPAA2 SoCs``. > + > +Port-core binding > +~~~~~~~~~~~~~~~~~ > + > +DPAA2 EVENTDEV driver requires event port 'x' to be used on core 'x'. Is it a HW limitation? or Is it like, only one port can connect to one lcore. If it latter, then I think, you can have physical port to virtual port translation in slow path as ports are enumerated as 0 to N. lcore id can be anything. > -- > 1.9.1 >
