From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>,
<ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] wifi: ath12k: refactor DP Rxdma ring structure
Date: Mon, 13 Nov 2023 07:23:27 -0800 [thread overview]
Message-ID: <13544bcb-9c8b-49cd-9b43-ebe2d2b96778@quicinc.com> (raw)
In-Reply-To: <20231111043934.20485-5-quic_periyasa@quicinc.com>
On 11/10/2023 8:39 PM, Karthikeyan Periyasamy wrote:
> Currently data path Rxdma ring structure store the IDR buffer and lock.
> These IDR handling is needed only for SW cookie conversion and not
> needed for HW cookie conversion. REO Rxdma ring use the HW cookie
> conversion and monitor Rxdma ring use the SW cookie conversion.
> Since idr not needed for REO Rxdma ring, remove the IDR data entity
> from the data path Rxdma ring structure. Introduce the new data path ring
> structure for monitor rxmda rings since it need IDR data entity.
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.1.1-00125-QCAHKSWPL_SILICONZ-1
>
> Signed-off-by: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
--
ath12k mailing list
ath12k@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/ath12k
prev parent reply other threads:[~2023-11-13 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 4:39 [PATCH v2 0/4] ath12k: Refactor Rxdma replenish arguments Karthikeyan Periyasamy
2023-11-11 4:39 ` [PATCH v2 1/4] wifi: ath12k: avoid explicit mac id argument in Rxdma replenish Karthikeyan Periyasamy
2023-11-13 15:21 ` Jeff Johnson
2023-11-29 11:27 ` Kalle Valo
2023-11-11 4:39 ` [PATCH v2 2/4] wifi: ath12k: avoid explicit RBM " Karthikeyan Periyasamy
2023-11-13 15:22 ` Jeff Johnson
2023-11-11 4:39 ` [PATCH v2 3/4] wifi: ath12k: avoid explicit HW conversion " Karthikeyan Periyasamy
2023-11-13 15:23 ` Jeff Johnson
2023-11-11 4:39 ` [PATCH v2 4/4] wifi: ath12k: refactor DP Rxdma ring structure Karthikeyan Periyasamy
2023-11-13 15:23 ` Jeff Johnson [this message]
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=13544bcb-9c8b-49cd-9b43-ebe2d2b96778@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_periyasa@quicinc.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