DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tejasree Kondoj <ktejasree@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Vidya Sagar Velumuri <vvelumuri@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>, <dev@dpdk.org>
Subject: [PATCH v2 04/25] crypto/cnxk: add cn20k datapath skeleton
Date: Tue, 3 Jun 2025 17:20:05 +0530	[thread overview]
Message-ID: <20250603115026.2664706-5-ktejasree@marvell.com> (raw)
In-Reply-To: <20250603115026.2664706-1-ktejasree@marvell.com>

From: Vidya Sagar Velumuri <vvelumuri@marvell.com>

Add skeleton for cn20k enqueue-dequeue functions

Signed-off-by: Vidya Sagar Velumuri <vvelumuri@marvell.com>
---
 drivers/crypto/cnxk/cn20k_cryptodev.c     |  1 +
 drivers/crypto/cnxk/cn20k_cryptodev_ops.c | 29 +++++++++++++++++++++++
 drivers/crypto/cnxk/cn20k_cryptodev_ops.h |  1 +
 3 files changed, 31 insertions(+)

diff --git a/drivers/crypto/cnxk/cn20k_cryptodev.c b/drivers/crypto/cnxk/cn20k_cryptodev.c
index 980ea7df97..4c70c15ca9 100644
--- a/drivers/crypto/cnxk/cn20k_cryptodev.c
+++ b/drivers/crypto/cnxk/cn20k_cryptodev.c
@@ -92,6 +92,7 @@ cn20k_cpt_pci_probe(struct rte_pci_driver *pci_drv __rte_unused, struct rte_pci_
 	dev->feature_flags = cnxk_cpt_default_ff_get();
 
 	dev->qp_depth_used = cnxk_cpt_qp_depth_used;
+	cn20k_cpt_set_enqdeq_fns(dev);
 
 	rte_cryptodev_pmd_probing_finish(dev);
 
diff --git a/drivers/crypto/cnxk/cn20k_cryptodev_ops.c b/drivers/crypto/cnxk/cn20k_cryptodev_ops.c
index ac321a2b91..37a4472e31 100644
--- a/drivers/crypto/cnxk/cn20k_cryptodev_ops.c
+++ b/drivers/crypto/cnxk/cn20k_cryptodev_ops.c
@@ -30,6 +30,35 @@ cn20k_cpt_crypto_adapter_ev_mdata_set(struct rte_cryptodev *dev __rte_unused, vo
 	return 0;
 }
 
+static uint16_t
+cn20k_cpt_enqueue_burst(void *qptr, struct rte_crypto_op **ops, uint16_t nb_ops)
+{
+	(void)qptr;
+	(void)ops;
+	(void)nb_ops;
+
+	return 0;
+}
+
+static uint16_t
+cn20k_cpt_dequeue_burst(void *qptr, struct rte_crypto_op **ops, uint16_t nb_ops)
+{
+	(void)qptr;
+	(void)ops;
+	(void)nb_ops;
+
+	return 0;
+}
+
+void
+cn20k_cpt_set_enqdeq_fns(struct rte_cryptodev *dev)
+{
+	dev->enqueue_burst = cn20k_cpt_enqueue_burst;
+	dev->dequeue_burst = cn20k_cpt_dequeue_burst;
+
+	rte_mb();
+}
+
 static void
 cn20k_cpt_dev_info_get(struct rte_cryptodev *dev, struct rte_cryptodev_info *info)
 {
diff --git a/drivers/crypto/cnxk/cn20k_cryptodev_ops.h b/drivers/crypto/cnxk/cn20k_cryptodev_ops.h
index d7c3aed22b..d9594513d1 100644
--- a/drivers/crypto/cnxk/cn20k_cryptodev_ops.h
+++ b/drivers/crypto/cnxk/cn20k_cryptodev_ops.h
@@ -20,4 +20,5 @@
 
 extern struct rte_cryptodev_ops cn20k_cpt_ops;
 
+void cn20k_cpt_set_enqdeq_fns(struct rte_cryptodev *dev);
 #endif /* _CN20K_CRYPTODEV_OPS_H_ */
-- 
2.25.1


  parent reply	other threads:[~2025-06-03 11:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 11:50 [PATCH v2 00/25] add CN20K support to cnxk crypto PMD Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 01/25] crypto/cnxk: probe cn20k device Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 02/25] crypto/cnxk: add cn20k ops skeleton Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 03/25] crypto/cnxk: add dev info get Tejasree Kondoj
2025-06-03 11:50 ` Tejasree Kondoj [this message]
2025-06-03 11:50 ` [PATCH v2 05/25] crypto/cnxk: add cn20k lmtst routines Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 06/25] crypto/cnxk: add cn20k enqueue path Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 07/25] crypto/cnxk: add cn20k dequeue path Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 08/25] crypto/cnxk: move debug dumps to common Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 09/25] crypto/cnxk: add cn20k security skeletion Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 10/25] crypto/cnxk: add security session creation Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 11/25] crypto/cnxk: add security session destroy Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 12/25] crypto/cnxk: move code to common Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 13/25] crypto/cnxk: add IPsec session update Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 14/25] crypto/cnxk: add security datapath Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 15/25] crypto/cnxk: add Rx inject in security lookaside Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 16/25] crypto/cnxk: add TLS skeleton Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 17/25] crypto/cnxk: add TLS read session Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 18/25] crypto/cnxk: add TLS write session Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 19/25] crypto/cnxk: add TLS session destroy Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 20/25] crypto/cnxk: add TLS datapath Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 21/25] crypto/cnxk: add TLS post process Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 22/25] crypto/cnxk: add TLS session update Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 23/25] crypto/cnxk: support raw API for cn20k Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 24/25] crypto/cnxk: add model check " Tejasree Kondoj
2025-06-03 11:50 ` [PATCH v2 25/25] doc: update cn20k CPT documentation Tejasree Kondoj
2025-06-03 14:25 ` [PATCH v2 00/25] add CN20K support to cnxk crypto PMD 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=20250603115026.2664706-5-ktejasree@marvell.com \
    --to=ktejasree@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=vvelumuri@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).