From: Hernan Vargas <hernan.vargas@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com,
maxime.coquelin@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com,
Hernan Vargas <hernan.vargas@intel.com>
Subject: [PATCH v1 06/10] baseband/acc: remove soft output bypass
Date: Fri, 30 Aug 2024 13:09:48 -0700 [thread overview]
Message-ID: <20240830200952.182685-7-hernan.vargas@intel.com> (raw)
In-Reply-To: <20240830200952.182685-1-hernan.vargas@intel.com>
Removing soft output bypass capability due to device limitations.
Signed-off-by: Hernan Vargas <hernan.vargas@intel.com>
---
drivers/baseband/acc/rte_vrb_pmd.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/baseband/acc/rte_vrb_pmd.c b/drivers/baseband/acc/rte_vrb_pmd.c
index 9beb05cd95cf..654b4d902732 100644
--- a/drivers/baseband/acc/rte_vrb_pmd.c
+++ b/drivers/baseband/acc/rte_vrb_pmd.c
@@ -1363,7 +1363,6 @@ vrb_dev_info_get(struct rte_bbdev *dev, struct rte_bbdev_driver_info *dev_info)
RTE_BBDEV_LDPC_HARQ_4BIT_COMPRESSION |
RTE_BBDEV_LDPC_LLR_COMPRESSION |
RTE_BBDEV_LDPC_SOFT_OUT_ENABLE |
- RTE_BBDEV_LDPC_SOFT_OUT_RM_BYPASS |
RTE_BBDEV_LDPC_SOFT_OUT_DEINTERLEAVER_BYPASS |
RTE_BBDEV_LDPC_DEC_INTERRUPTS,
.llr_size = 8,
@@ -1752,18 +1751,18 @@ vrb_fcw_ld_fill(struct rte_bbdev_dec_op *op, struct acc_fcw_ld *fcw,
fcw->so_en = check_bit(op->ldpc_dec.op_flags, RTE_BBDEV_LDPC_SOFT_OUT_ENABLE);
fcw->so_bypass_intlv = check_bit(op->ldpc_dec.op_flags,
RTE_BBDEV_LDPC_SOFT_OUT_DEINTERLEAVER_BYPASS);
- fcw->so_bypass_rm = check_bit(op->ldpc_dec.op_flags,
- RTE_BBDEV_LDPC_SOFT_OUT_RM_BYPASS);
+ fcw->so_bypass_rm = 0;
fcw->minsum_offset = 1;
fcw->dec_llrclip = 2;
}
/*
- * These are all implicitly set
+ * These are all implicitly set:
* fcw->synd_post = 0;
* fcw->dec_convllr = 0;
* fcw->hcout_convllr = 0;
* fcw->hcout_size1 = 0;
+ * fcw->so_it = 0;
* fcw->hcout_offset = 0;
* fcw->negstop_th = 0;
* fcw->negstop_it = 0;
--
2.37.1
next prev parent reply other threads:[~2024-08-30 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 20:09 [PATCH v1 00/10] acc baseband PMD fix and updates for 24.11 Hernan Vargas
2024-08-30 20:09 ` [PATCH v1 01/10] baseband/acc: fix access to deallocated mem Hernan Vargas
2024-09-13 14:49 ` Maxime Coquelin
2024-08-30 20:09 ` [PATCH v1 02/10] baseband/acc: queue allocation refactor Hernan Vargas
2024-08-30 20:09 ` [PATCH v1 03/10] baseband/acc: configure max queues per device Hernan Vargas
2024-08-30 20:09 ` [PATCH v1 04/10] baseband/acc: future proof structure comparison Hernan Vargas
2024-08-30 20:09 ` [PATCH v1 05/10] baseband/acc: enhance SW ring alignment Hernan Vargas
2024-08-30 20:09 ` Hernan Vargas [this message]
2024-08-30 20:09 ` [PATCH v1 07/10] baseband/acc: algorithm tuning for LDPC decoder Hernan Vargas
2024-08-30 20:09 ` [PATCH v1 08/10] baseband/acc: remove check on HARQ memory Hernan Vargas
2024-08-30 20:09 ` [PATCH v1 09/10] baseband/acc: reset ring data valid bit Hernan Vargas
2024-08-30 20:09 ` [PATCH v1 10/10] baseband/acc: cosmetic changes Hernan Vargas
2024-08-30 20:23 ` [PATCH v1 00/10] acc baseband PMD fix and updates for 24.11 Vargas, Hernan
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=20240830200952.182685-7-hernan.vargas@intel.com \
--to=hernan.vargas@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=trix@redhat.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).