From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware
Date: Thu, 4 Apr 2019 07:23:14 +0000 [thread overview]
Message-ID: <20190404072335.24555-1-shreyansh.jain@nxp.com> (raw)
Message-ID: <20190404072314.t6f48ZTXwS3p-JJXQsbrFfcSl94QXItJGU0qpwbbrhk@z> (raw)
In-Reply-To: <20190403142357.17700-1-shreyansh.jain@nxp.com>
Based on net-next: 69f805ac18abe
All the patches are strictly within DPAA2/FSLMC driver area.
MC firmware is the core component of FSLMC bus which enables
all the dpaa2 devices (eth, crypto etc).
With recent release of NXP's layerscape SDK, the MC firmware
has been bumped up. These patches updates only necessary
changes so as to maintain version compatibility.
v1->v2:
- In last patch (patch 2), one of a recent fix (e94be227b7)
was overwritten. Restoring that change.
Shreyansh Jain (3):
bus/fslmc: cleanup unused firmware code
drivers: update MC firmware version for FSLMC bus
doc: bump SDK support version for dpaa2
doc/guides/nics/dpaa2.rst | 4 +-
drivers/bus/fslmc/mc/dpci.c | 75 --------------------------
drivers/bus/fslmc/mc/dpcon.c | 30 -----------
drivers/bus/fslmc/mc/fsl_dpci.h | 21 --------
drivers/bus/fslmc/mc/fsl_dpcon.h | 19 -------
drivers/bus/fslmc/mc/fsl_dpmng.h | 2 +-
drivers/net/dpaa2/dpaa2_ethdev.c | 1 +
drivers/net/dpaa2/mc/dpni.c | 13 ++++-
drivers/net/dpaa2/mc/fsl_dpni.h | 84 ++++++++++++++++++++++-------
drivers/net/dpaa2/mc/fsl_dpni_cmd.h | 40 ++++++++++----
10 files changed, 111 insertions(+), 178 deletions(-)
--
2.19.1
next prev parent reply other threads:[~2019-04-04 7:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:23 [dpdk-dev] [PATCH " Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` [dpdk-dev] [PATCH 1/3] bus/fslmc: cleanup unused firmware code Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` [dpdk-dev] [PATCH 2/3] drivers: update MC firmware version for FSLMC bus Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` [dpdk-dev] [PATCH 3/3] doc: bump SDK support version for dpaa2 Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain [this message]
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 1/3] bus/fslmc: cleanup unused firmware code Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 21:29 ` Ferruh Yigit
2019-04-04 21:29 ` Ferruh Yigit
2019-04-04 21:43 ` Thomas Monjalon
2019-04-04 21:43 ` Thomas Monjalon
2019-04-05 11:19 ` Shreyansh Jain
2019-04-05 11:19 ` Shreyansh Jain
2019-04-05 11:37 ` Ferruh Yigit
2019-04-05 11:37 ` Ferruh Yigit
2019-04-05 11:38 ` Shreyansh Jain
2019-04-05 11:38 ` Shreyansh Jain
2019-04-05 12:35 ` Thomas Monjalon
2019-04-05 12:35 ` Thomas Monjalon
2019-04-05 12:58 ` Shreyansh Jain
2019-04-05 12:58 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 2/3] drivers: update MC firmware version for FSLMC bus Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 3/3] doc: bump SDK support version for dpaa2 Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 21:08 ` [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware Thomas Monjalon
2019-04-04 21:08 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190404072335.24555-1-shreyansh.jain@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).