DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gagandeep Singh <G.Singh@nxp.com>
To: "Hemant Agrawal (OSS)" <hemant.agrawal@oss.nxp.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: RE: [PATCH 6/9] crypto/dpaa2_sec: add null algo capability
Date: Wed, 21 May 2025 04:51:33 +0000	[thread overview]
Message-ID: <AS8PR04MB8198741771B80D7049E2CD4CE19EA@AS8PR04MB8198.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <3c0a10d2-83ec-963e-66b5-34f7c0bd9404@oss.nxp.com>

Hi,

> -----Original Message-----
> From: Hemant Agrawal (OSS) <hemant.agrawal@oss.nxp.com>
> Sent: Tuesday, May 20, 2025 11:50 AM
> To: Gagandeep Singh <G.Singh@nxp.com>; dev@dpdk.org; Hemant Agrawal
> <hemant.agrawal@nxp.com>
> Subject: Re: [PATCH 6/9] crypto/dpaa2_sec: add null algo capability
> 
> 
> On 20-05-2025 11:21, Gagandeep Singh wrote:
> > This patch adds NULL algo capabilities.
> Do you also need to update documentation for the same?
Yes, I will send the update in next version.

> >
> > Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> > ---
> >   drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h | 41 +++++++++++++++++++++++
> >   1 file changed, 41 insertions(+)
> >
> > diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h
> b/drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h
> > index 1c0bc3d6de..e9b601c035 100644
> > --- a/drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h
> > +++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h
> > @@ -227,6 +227,27 @@ typedef struct dpaa2_sec_session_entry {
> >
> >   static const struct rte_cryptodev_capabilities dpaa2_sec_capabilities[] = {
> >   	/* Symmetric capabilities */
> > +	{	/* NULL (AUTH) */
> > +		.op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
> > +		{.sym = {
> > +			.xform_type = RTE_CRYPTO_SYM_XFORM_AUTH,
> > +			{.auth = {
> > +				.algo = RTE_CRYPTO_AUTH_NULL,
> > +				.block_size = 1,
> > +				.key_size = {
> > +					.min = 0,
> > +					.max = 0,
> > +					.increment = 0
> > +				},
> > +				.digest_size = {
> > +					.min = 0,
> > +					.max = 0,
> > +					.increment = 0
> > +				},
> > +				.iv_size = { 0 }
> > +			}, },
> > +		}, },
> > +	},
> >   	{	/* MD5 */
> >   		.op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
> >   		{.sym = {
> > @@ -553,6 +574,26 @@ static const struct rte_cryptodev_capabilities
> dpaa2_sec_capabilities[] = {
> >   			}, }
> >   		}, }
> >   	},
> > +	{	/* NULL (CIPHER) */
> > +		.op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
> > +		{.sym = {
> > +			.xform_type = RTE_CRYPTO_SYM_XFORM_CIPHER,
> > +			{.cipher = {
> > +				.algo = RTE_CRYPTO_CIPHER_NULL,
> > +				.block_size = 1,
> > +				.key_size = {
> > +					.min = 0,
> > +					.max = 0,
> > +					.increment = 0
> > +				},
> > +				.iv_size = {
> > +					.min = 0,
> > +					.max = 0,
> > +					.increment = 0
> > +				}
> > +			}, },
> > +		}, }
> > +	},
> >   	{	/* AES CBC */
> >   		.op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
> >   		{.sym = {

  reply	other threads:[~2025-05-21  4:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20  5:51 [PATCH 1/9] common/dpaax: fix invalid key command error Gagandeep Singh
2025-05-20  5:51 ` [PATCH 2/9] common/dpaax: fix for PDCP AES only 12bit SN case Gagandeep Singh
2025-05-20  5:51 ` [PATCH 3/9] common/dpaax: support 12bit SN in pdcp uplane Gagandeep Singh
2025-05-20  6:18   ` Hemant Agrawal
2025-05-21  4:50     ` Gagandeep Singh
2025-05-20  5:51 ` [PATCH 4/9] crypto/dpaa2_sec: change custom device API to standard Gagandeep Singh
2025-05-20  5:51 ` [PATCH 5/9] crypto/dpaa2_sec: fix coverity Issues Gagandeep Singh
2025-05-20  5:51 ` [PATCH 6/9] crypto/dpaa2_sec: add null algo capability Gagandeep Singh
2025-05-20  6:20   ` Hemant Agrawal
2025-05-21  4:51     ` Gagandeep Singh [this message]
2025-05-20  5:51 ` [PATCH 7/9] net/dpaa2: configure buffer layout Gagandeep Singh
2025-05-20  5:51 ` [PATCH 8/9] mempool/dpaa2: mempool operation index Gagandeep Singh
2025-05-20  5:51 ` [PATCH 9/9] crypto/dpaa2_sec: add support for simple IPsec FD Gagandeep Singh
2025-05-20  6:16 ` [PATCH 1/9] common/dpaax: fix invalid key command error Hemant Agrawal
2025-05-21  4:43   ` Gagandeep Singh
2025-05-21  6:56 ` [PATCH v2 0/9] DPAA2 crypto driver changes Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 1/9] common/dpaax: fix invalid key command error Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 2/9] common/dpaax: fix for PDCP AES only 12bit SN case Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 3/9] common/dpaax: support 12bit SN in pdcp uplane Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 4/9] crypto/dpaa2_sec: change custom device API to standard Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 5/9] crypto/dpaa2_sec: fix coverity Issues Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 6/9] crypto/dpaa2_sec: add null algo capability Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 7/9] net/dpaa2: configure buffer layout Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 8/9] mempool/dpaa2: mempool operation index Gagandeep Singh
2025-05-21  6:56   ` [PATCH v2 9/9] crypto/dpaa2_sec: add support for simple IPsec FD Gagandeep Singh
2025-05-21 11:59   ` [EXTERNAL] [PATCH v2 0/9] DPAA2 crypto driver changes 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=AS8PR04MB8198741771B80D7049E2CD4CE19EA@AS8PR04MB8198.eurprd04.prod.outlook.com \
    --to=g.singh@nxp.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=hemant.agrawal@oss.nxp.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).