From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Gagandeep Singh <g.singh@nxp.com>,
dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
Sachin Saxena <sachin.saxena@nxp.com>
Subject: Re: [PATCH 3/9] common/dpaax: support 12bit SN in pdcp uplane
Date: Tue, 20 May 2025 11:48:51 +0530 [thread overview]
Message-ID: <9e4ce500-e3e6-86a5-008c-013c8ff313af@oss.nxp.com> (raw)
In-Reply-To: <20250520055133.506071-3-g.singh@nxp.com>
On 20-05-2025 11:21, Gagandeep Singh wrote:
> update pdcp_insert_uplane_no_int_op() to support 12bit SN size
>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> ---
> drivers/common/dpaax/caamflib/desc/pdcp.h | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/common/dpaax/caamflib/desc/pdcp.h b/drivers/common/dpaax/caamflib/desc/pdcp.h
> index c90eff26a8..55159d53f0 100644
> --- a/drivers/common/dpaax/caamflib/desc/pdcp.h
> +++ b/drivers/common/dpaax/caamflib/desc/pdcp.h
> @@ -1988,10 +1988,10 @@ pdcp_insert_uplane_no_int_op(struct program *p,
> return 0;
> }
>
> - if (sn_size == PDCP_SN_SIZE_15) {
> + if (sn_size == PDCP_SN_SIZE_12) {
> SEQLOAD(p, MATH0, 6, 2, 0);
> - sn_mask = (swap == false) ? PDCP_U_PLANE_15BIT_SN_MASK :
> - PDCP_U_PLANE_15BIT_SN_MASK_BE;
> + sn_mask = (swap == false) ? PDCP_12BIT_SN_MASK :
> + PDCP_12BIT_SN_MASK_BE;
how the 15 bit will be handled now?
> } else { /* SN Size == PDCP_SN_SIZE_18 */
> SEQLOAD(p, MATH0, 5, 3, 0);
> sn_mask = (swap == false) ? PDCP_U_PLANE_18BIT_SN_MASK :
> @@ -2000,7 +2000,7 @@ pdcp_insert_uplane_no_int_op(struct program *p,
> JUMP(p, 1, LOCAL_JUMP, ALL_TRUE, CALM);
> MATHB(p, MATH0, AND, sn_mask, MATH1, 8, IFB | IMMED2);
>
> - if (sn_size == PDCP_SN_SIZE_15)
> + if (sn_size == PDCP_SN_SIZE_12)
> SEQSTORE(p, MATH0, 6, 2, 0);
> else /* SN Size == PDCP_SN_SIZE_18 */
> SEQSTORE(p, MATH0, 5, 3, 0);
> @@ -2047,7 +2047,7 @@ pdcp_insert_uplane_no_int_op(struct program *p,
>
> default:
> pr_err("%s: Invalid encrypt algorithm selected: %d\n",
> - "pdcp_insert_uplane_15bit_op", cipherdata->algtype);
> + "pdcp_insert_uplane_no_int_op", cipherdata->algtype);
Why not use DPDK LOG APIs?
also, why not use __func__ ?
> return -EINVAL;
> }
>
> @@ -2734,8 +2734,7 @@ cnstr_shdsc_pdcp_u_plane_encap(uint32_t *descbuf,
> cipherdata->algtype == PDCP_CIPHER_TYPE_AES
> && !authdata
> && sn_size == PDCP_SN_SIZE_12) {
> - err = pdcp_insert_cplane_enc_only_op(p, swap, cipherdata,
> - authdata,
> + err = pdcp_insert_uplane_no_int_op(p, swap, cipherdata,
> OP_TYPE_ENCAP_PROTOCOL, sn_size);
> if (err)
> return err;
next prev parent reply other threads:[~2025-05-20 6:19 UTC|newest]
Thread overview: 12+ 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 [this message]
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-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
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=9e4ce500-e3e6-86a5-008c-013c8ff313af@oss.nxp.com \
--to=hemant.agrawal@oss.nxp.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=sachin.saxena@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).