call to dpaa2_sec_dev_configure() is made mandatory,
but dpaa2_sec_pmd returns a ENOTSUP which results in
device not getting configured.
dpaa2_sec PMD does not need any further configuration
to be done in dpaa2_sec_dev_configure, hence returning 0
Fixes: e5cbdfc53765 ("crypto/dpaa2_sec: add basic operations")
Signed-off-by: Akhil Goyal <akhil.go...@nxp.com>
---
This patch is for stable 17.05 tree only.
This fix is already present in dpdk mainline
drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
index 4e01fe8..08fd085 100644
--- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
+++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
@@ -1263,7 +1263,7 @@ dpaa2_sec_dev_configure(struct rte_cryptodev *dev
__rte_unused,
{
PMD_INIT_FUNC_TRACE();
- return -ENOTSUP;
+ return 0;
}
static int
--
2.9.3
