From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: kangyang <quic_kangyang@quicinc.com>, <ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 09/11] wifi: ath12k: use tail MSDU to get MSDU information
Date: Thu, 25 Jul 2024 17:17:59 -0700 [thread overview]
Message-ID: <3a0a2d45-ef8a-4bd4-9931-eec88dcd4dee@quicinc.com> (raw)
In-Reply-To: <20240725120035.493-10-quic_kangyang@quicinc.com>
On 7/25/2024 5:00 AM, kangyang wrote:
> From: Kang Yang <quic_kangyang@quicinc.com>
>
> When receiving a packet in monitor mode, hardware will fill status
> information msdu_end for MSDUs. Then host can use these status
> information to get specific information about this packet, such as
> l3 offset, bandwidth, mcs, packet type.
>
> If this packet is composed of multiple MSDUs, then hardware will only
> fill status information for the last(tail) MSDU. At this time,
> MSDU information is uncertain for others MSDUs. But current code use
> the first MSDU in monitor mode, so will get the wrong information.
>
> Fix it by getting msdu information from last(tail) msdu.
>
> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
>
> Signed-off-by: Kang Yang <quic_kangyang@quicinc.com>
Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
next prev parent reply other threads:[~2024-07-26 0:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 12:00 [PATCH 00/11] wifi: ath12k: some fixes and clean up for monitor mode kangyang
2024-07-25 12:00 ` [PATCH 01/11] wifi: ath12k: remove unused variable monitor_present kangyang
2024-07-26 0:11 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 02/11] wifi: ath12k: optimize storage size for struct ath12k kangyang
2024-07-26 0:13 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 03/11] wifi: ath12k: fix struct hal_rx_ppdu_end_user_stats kangyang
2024-07-26 0:14 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 04/11] wifi: ath12k: fix struct hal_rx_ppdu_start kangyang
2024-07-26 0:17 ` Jeff Johnson
2024-07-31 11:17 ` Kalle Valo
2024-07-31 11:22 ` Kalle Valo
2024-07-31 13:55 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 05/11] wifi: ath12k: fix struct hal_rx_phyrx_rssi_legacy_info kangyang
2024-07-26 0:17 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 06/11] wifi: ath12k: fix struct hal_rx_mpdu_start kangyang
2024-07-26 0:17 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 07/11] wifi: ath12k: properly handling the state variables of monitor mode kangyang
2024-07-26 0:17 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 08/11] wifi: ath12k: delete NSS and TX power setting for monitor vdev kangyang
2024-07-26 0:17 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 09/11] wifi: ath12k: use tail MSDU to get MSDU information kangyang
2024-07-26 0:17 ` Jeff Johnson [this message]
2024-07-25 12:00 ` [PATCH 10/11] wifi: ath12k: fix A-MSDU indication in monitor mode kangyang
2024-07-26 0:18 ` Jeff Johnson
2024-07-25 12:00 ` [PATCH 11/11] wifi: ath12k: delete mon reap timer kangyang
2024-07-26 0:18 ` Jeff Johnson
[not found] ` <52318022dbe745da8b18892c26d78bec@realtek.com>
2024-07-26 17:04 ` Jeff Johnson
2024-07-26 17:02 ` Jeff Johnson
2024-07-26 0:11 ` [PATCH 00/11] wifi: ath12k: some fixes and clean up for monitor mode Jeff Johnson
2024-07-31 11:19 ` Kalle Valo
2024-08-01 6:08 ` Kang Yang
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=3a0a2d45-ef8a-4bd4-9931-eec88dcd4dee@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_kangyang@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