crypto/qat: unify symmetric functions

[dpdk.git] / drivers / crypto / qat / qat_asym_pmd.h

diff --git a/drivers/crypto/qat/qat_asym_pmd.h b/drivers/crypto/qat/qat_asym_pmd.h
index 3b5abdd..f988d64 100644 (file)
--- a/drivers/crypto/qat/qat_asym_pmd.h
+++ b/drivers/crypto/qat/qat_asym_pmd.h
@@ -7,29 +7,41 @@
 #define _QAT_ASYM_PMD_H_
 
 #include <rte_cryptodev.h>
+#include "qat_crypto.h"
 #include "qat_device.h"
 
-/** Intel(R) QAT Asymmetric Crypto PMD driver name */
+/** Intel(R) QAT Asymmetric Crypto PMD name */
 #define CRYPTODEV_NAME_QAT_ASYM_PMD    crypto_qat_asym
 
 
+/**
+ * Helper function to add an asym capability
+ * <name> <op type> <modlen (min, max, increment)>
+ **/
+#define QAT_ASYM_CAP(n, o, l, r, i)                                    \
+       {                                                               \
+               .op = RTE_CRYPTO_OP_TYPE_ASYMMETRIC,                    \
+               {.asym = {                                              \
+                       .xform_capa = {                                 \
+                               .xform_type = RTE_CRYPTO_ASYM_XFORM_##n,\
+                               .op_types = o,                          \
+                               {                                       \
+                               .modlen = {                             \
+                               .min = l,                               \
+                               .max = r,                               \
+                               .increment = i                          \
+                               }, }                                    \
+                       }                                               \
+               },                                                      \
+               }                                                       \
+       }
+
 extern uint8_t qat_asym_driver_id;
 
-/** private data structure for a QAT device.
- * This QAT device is a device offering only asymmetric crypto service,
- * there can be one of these on each qat_pci_device (VF).
- */
-struct qat_asym_dev_private {
-       struct qat_pci_device *qat_dev;
-       /**< The qat pci device hosting the service */
-       uint8_t asym_dev_id;
-       /**< Device instance for this rte_cryptodev */
-       const struct rte_cryptodev_capabilities *qat_dev_capabilities;
-       /* QAT device asymmetric crypto capabilities */
-       const struct rte_memzone *capa_mz;
-       /* Shared memzone for storing capabilities */
-       uint16_t min_enq_burst_threshold;
-};
+extern struct qat_crypto_gen_dev_ops qat_asym_gen_dev_ops[];
+
+void
+qat_asym_init_op_cookie(void *op_cookie);
 
 uint16_t
 qat_asym_pmd_enqueue_op_burst(void *qp, struct rte_crypto_op **ops,
@@ -39,16 +51,4 @@ uint16_t
 qat_asym_pmd_dequeue_op_burst(void *qp, struct rte_crypto_op **ops,
                              uint16_t nb_ops);
 
-int qat_asym_session_configure(struct rte_cryptodev *dev,
-               struct rte_crypto_asym_xform *xform,
-               struct rte_cryptodev_asym_session *sess,
-               struct rte_mempool *mempool);
-
-int
-qat_asym_dev_create(struct qat_pci_device *qat_pci_dev,
-               struct qat_dev_cmd_param *qat_dev_cmd_param);
-
-int
-qat_asym_dev_destroy(struct qat_pci_device *qat_pci_dev);
-
 #endif /* _QAT_ASYM_PMD_H_ */