DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anoob Joseph <anoobj@marvell.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Lukasz Bartosik <lbartosik@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>,
	 Narayana Prasad <pathreya@marvell.com>, <dev@dpdk.org>,
	Anoob Joseph <anoobj@marvell.com>
Subject: [dpdk-dev] [PATCH v2] crypto/octeontx: sync mbox changes done in kernel driver
Date: Wed, 29 May 2019 16:14:03 +0530	[thread overview]
Message-ID: <1559126643-29933-1-git-send-email-anoobj@marvell.com> (raw)
In-Reply-To: <1559126183-29543-1-git-send-email-anoobj@marvell.com>

From: Lukasz Bartosik <lbartosik@marvell.com>

Synchronize mbox with latest changes in kernel driver

Signed-off-by: Lukasz Bartosik <lbartosik@marvell.com>
Signed-off-by: Anoob Joseph <anoobj@marvell.com>
---
 drivers/crypto/octeontx/otx_cryptodev_mbox.c |  3 +++
 drivers/crypto/octeontx/otx_cryptodev_mbox.h | 12 +++++-------
 2 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/drivers/crypto/octeontx/otx_cryptodev_mbox.c b/drivers/crypto/octeontx/otx_cryptodev_mbox.c
index a8e51a8..daba776 100644
--- a/drivers/crypto/octeontx/otx_cryptodev_mbox.c
+++ b/drivers/crypto/octeontx/otx_cryptodev_mbox.c
@@ -24,6 +24,9 @@ otx_cpt_handle_mbox_intr(struct cpt_vf *cptvf)
 	CPT_LOG_DP_DEBUG("%s: Mailbox msg 0x%lx from PF",
 		    cptvf->dev_name, (unsigned int long)mbx.msg);
 	switch (mbx.msg) {
+	case OTX_CPT_MSG_VF_UP:
+		cptvf->pf_acked = true;
+		break;
 	case OTX_CPT_MSG_READY:
 		{
 			otx_cpt_chipid_vfid_t cid;
diff --git a/drivers/crypto/octeontx/otx_cryptodev_mbox.h b/drivers/crypto/octeontx/otx_cryptodev_mbox.h
index b05d1c5..2d2e0e6 100644
--- a/drivers/crypto/octeontx/otx_cryptodev_mbox.h
+++ b/drivers/crypto/octeontx/otx_cryptodev_mbox.h
@@ -15,11 +15,6 @@
 
 #define OTX_CPT_MBOX_MSG_TIMEOUT    2000 /* In Milli Seconds */
 
-#define OTX_CPT_MBOX_MSG_TYPE_REQ	0
-#define OTX_CPT_MBOX_MSG_TYPE_ACK	1
-#define OTX_CPT_MBOX_MSG_TYPE_NACK	2
-#define OTX_CPT_MBOX_MSG_TYPE_NOP	3
-
 /* CPT mailbox structure */
 struct cpt_mbox {
 	/** Message type MBOX[0] */
@@ -28,7 +23,8 @@ struct cpt_mbox {
 	uint64_t data;
 };
 
-typedef enum {
+/* PF-VF message opcodes */
+enum otx_cpt_mbox_opcode {
 	OTX_CPT_MSG_VF_UP = 1,
 	OTX_CPT_MSG_VF_DOWN,
 	OTX_CPT_MSG_READY,
@@ -36,7 +32,9 @@ typedef enum {
 	OTX_CPT_MSG_QBIND_GRP,
 	OTX_CPT_MSG_VQ_PRIORITY,
 	OTX_CPT_MSG_PF_TYPE,
-} otx_cpt_mbox_opcode_t;
+	OTX_CPT_MBOX_MSG_TYPE_ACK,
+	OTX_CPT_MBOX_MSG_TYPE_NACK
+};
 
 typedef union {
 	uint64_t u64;
-- 
2.7.4


  reply	other threads:[~2019-05-29 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 10:36 [dpdk-dev] [PATCH] crypto/octeontx: sync mbox changes done in kernel drv Anoob Joseph
2019-05-29 10:44 ` Anoob Joseph [this message]
2019-06-11  3:34   ` [dpdk-dev] [PATCH v2] crypto/octeontx: sync mbox changes done in kernel driver Anoob Joseph
2019-06-19 14:49   ` Akhil Goyal

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=1559126643-29933-1-git-send-email-anoobj@marvell.com \
    --to=anoobj@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=lbartosik@marvell.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=pathreya@marvell.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).