From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>, dev@dpdk.org
Cc: hemant.agrawal@nxp.com, david.marchand@redhat.com,
hernan.vargas@intel.com
Subject: Re: [PATCH v1 1/3] bbdev: new k0 parameter for LDPC decoder operation
Date: Thu, 29 Aug 2024 10:00:27 +0200 [thread overview]
Message-ID: <15d5518a-a636-4b7a-852d-075fb7622178@redhat.com> (raw)
In-Reply-To: <20240701212703.417094-2-nicolas.chautru@intel.com>
Hi,
On 7/1/24 23:27, Nicolas Chautru wrote:
> In latest 3GPP 38.212, the k0 value is not necessaraly directly
necessarily*
> derived from rv_index, in that case a value can be provided in
> API. When this value is non null this would override the value
> which would be computed purely from rv_index.
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
> doc/guides/prog_guide/bbdev.rst | 2 ++
> lib/bbdev/rte_bbdev_op.h | 4 ++++
> 2 files changed, 6 insertions(+)
>
> diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
> index 09e5f0d990..e3f356450b 100644
> --- a/doc/guides/prog_guide/bbdev.rst
> +++ b/doc/guides/prog_guide/bbdev.rst
> @@ -1021,6 +1021,8 @@ The LDPC decode parameters are set out in the table below.
> +----------------+------------+-------------------------------------------------------+
> | |eb |Eb, length of the RM output sequence in bits r >= cab |
> +----------------+------------+-------------------------------------------------------+
> +| |k0 |Optional k0 Rate matching starting position override |
> ++----------------+------------+-------------------------------------------------------+
>
> The mbuf input ``input`` encoded CB data is mandatory for all BBDEV PMDs
> and is the Virtual Circular Buffer data stream with null padding.
> diff --git a/lib/bbdev/rte_bbdev_op.h b/lib/bbdev/rte_bbdev_op.h
> index 459631d0d0..b5dde116ab 100644
> --- a/lib/bbdev/rte_bbdev_op.h
> +++ b/lib/bbdev/rte_bbdev_op.h
> @@ -562,6 +562,10 @@ struct rte_bbdev_op_ldpc_dec {
> /** Struct which stores Transport Block specific parameters */
> struct rte_bbdev_op_dec_ldpc_tb_params tb_params;
> };
> + /** Optional k0 Rate matching starting position, overrides rv_index when non null
> + * [3GPP TS38.212, section 5.4.2.1]
> + */
> + uint16_t k0;
> };
> /* >8 End of structure rte_bbdev_op_ldpc_dec. */
>
Will fix the typo while applying.
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Also reporting Hemant's Ack on the cover letter as patchwork doesn't
report them:
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Thanks,
Maxime
next prev parent reply other threads:[~2024-08-29 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 21:27 [PATCH v1 0/3] bbdev: new k0 parameter Nicolas Chautru
2024-07-01 21:27 ` [PATCH v1 1/3] bbdev: new k0 parameter for LDPC decoder operation Nicolas Chautru
2024-08-29 8:00 ` Maxime Coquelin [this message]
2024-07-01 21:27 ` [PATCH v1 2/3] test/bbdev: add support for k0 parameter Nicolas Chautru
2024-08-29 8:01 ` Maxime Coquelin
2024-07-01 21:27 ` [PATCH v1 3/3] baseband/acc: " Nicolas Chautru
2024-08-29 8:01 ` Maxime Coquelin
2024-07-02 6:50 ` [PATCH v1 0/3] bbdev: new " Hemant Agrawal
2024-09-13 13:50 ` Maxime Coquelin
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=15d5518a-a636-4b7a-852d-075fb7622178@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=nicolas.chautru@intel.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).