From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com, akhil.goyal@nxp.com,
stable@dpdk.org, Nipun Gupta <nipun.gupta@nxp.com>
Subject: [dpdk-dev] [PATCH 2/4] crypto/dpaa_sec: fix HMAC supported digest sizes
Date: Thu, 19 Apr 2018 22:22:37 +0530 [thread overview]
Message-ID: <1524156759-12931-2-git-send-email-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <1524156759-12931-1-git-send-email-hemant.agrawal@nxp.com>
For HMAC algorithms (MD5-HMAC, SHAx-HMAC), the supported
digest sizes are not a fixed value, but a range between
1 and the maximum digest size for those algorithms.
Also setting iv_size as 0.
Fixes: c3e85bdcc6e6 ("crypto/dpaa_sec: add crypto driver for NXP DPAA platform")
Cc: stable@dpdk.org
Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
drivers/crypto/dpaa_sec/dpaa_sec.h | 30 ++++++++++++++++++------------
1 file changed, 18 insertions(+), 12 deletions(-)
diff --git a/drivers/crypto/dpaa_sec/dpaa_sec.h b/drivers/crypto/dpaa_sec/dpaa_sec.h
index b8f7bd2..1433595 100644
--- a/drivers/crypto/dpaa_sec/dpaa_sec.h
+++ b/drivers/crypto/dpaa_sec/dpaa_sec.h
@@ -185,10 +185,11 @@ static const struct rte_cryptodev_capabilities dpaa_sec_capabilities[] = {
.increment = 1
},
.digest_size = {
- .min = 16,
+ .min = 1,
.max = 16,
- .increment = 0
+ .increment = 1
},
+ .iv_size = { 0 }
}, }
}, }
},
@@ -205,10 +206,11 @@ static const struct rte_cryptodev_capabilities dpaa_sec_capabilities[] = {
.increment = 1
},
.digest_size = {
- .min = 20,
+ .min = 1,
.max = 20,
- .increment = 0
+ .increment = 1
},
+ .iv_size = { 0 }
}, }
}, }
},
@@ -225,10 +227,11 @@ static const struct rte_cryptodev_capabilities dpaa_sec_capabilities[] = {
.increment = 1
},
.digest_size = {
- .min = 28,
+ .min = 1,
.max = 28,
- .increment = 0
+ .increment = 1
},
+ .iv_size = { 0 }
}, }
}, }
},
@@ -245,10 +248,11 @@ static const struct rte_cryptodev_capabilities dpaa_sec_capabilities[] = {
.increment = 1
},
.digest_size = {
- .min = 32,
+ .min = 1,
.max = 32,
- .increment = 0
+ .increment = 1
},
+ .iv_size = { 0 }
}, }
}, }
},
@@ -265,10 +269,11 @@ static const struct rte_cryptodev_capabilities dpaa_sec_capabilities[] = {
.increment = 1
},
.digest_size = {
- .min = 48,
+ .min = 1,
.max = 48,
- .increment = 0
+ .increment = 1
},
+ .iv_size = { 0 }
}, }
}, }
},
@@ -285,10 +290,11 @@ static const struct rte_cryptodev_capabilities dpaa_sec_capabilities[] = {
.increment = 1
},
.digest_size = {
- .min = 64,
+ .min = 1,
.max = 64,
- .increment = 0
+ .increment = 1
},
+ .iv_size = { 0 }
}, }
}, }
},
--
2.7.4
next prev parent reply other threads:[~2018-04-19 16:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 16:52 [dpdk-dev] [PATCH 1/4] crypto/dpaa_sec: support dynamic logging Hemant Agrawal
2018-04-19 16:52 ` Hemant Agrawal [this message]
2018-04-20 10:35 ` [dpdk-dev] [PATCH 2/4] crypto/dpaa_sec: fix HMAC supported digest sizes Akhil Goyal
2018-04-19 16:52 ` [dpdk-dev] [PATCH 3/4] crypto/dpaa2_sec: " Hemant Agrawal
2018-04-20 10:36 ` Akhil Goyal
2018-04-19 16:52 ` [dpdk-dev] [PATCH 4/4] crypto/dpaa_sec: update maximum queue pairs to 2 Hemant Agrawal
2018-04-20 9:47 ` De Lara Guarch, Pablo
2018-04-20 10:22 ` Akhil Goyal
2018-04-20 10:20 ` Akhil Goyal
2018-04-20 10:23 ` Hemant Agrawal
2018-04-20 10:40 ` Akhil Goyal
2018-04-20 16:00 ` De Lara Guarch, Pablo
2018-05-07 13:39 ` De Lara Guarch, Pablo
2018-05-08 11:24 ` [dpdk-dev] [PATCH v2] crypto/dpaa_sec: update maximum queue pairs to 8 Hemant Agrawal
2018-05-09 7:06 ` Akhil Goyal
2018-05-09 8:05 ` De Lara Guarch, Pablo
2018-04-20 10:35 ` [dpdk-dev] [PATCH 1/4] crypto/dpaa_sec: support dynamic logging Akhil Goyal
2018-04-20 16:09 ` De Lara Guarch, Pablo
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=1524156759-12931-2-git-send-email-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=nipun.gupta@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.org \
/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).