From: Kalle Valo <kvalo@kernel.org>
To: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: Re: [PATCH v3 2/8] wifi: ath12k: Refactor monitor status TLV structure
Date: Tue, 17 Dec 2024 21:47:13 +0200 [thread overview]
Message-ID: <878qseks72.fsf@kernel.org> (raw)
In-Reply-To: <20241217084511.2981515-3-quic_periyasa@quicinc.com> (Karthikeyan Periyasamy's message of "Tue, 17 Dec 2024 14:15:05 +0530")
Karthikeyan Periyasamy <quic_periyasa@quicinc.com> writes:
> The following TLV structures and bitmask definitions were inherited from
> the ath11k but were not updated for the ath12k 802.11be hardware. These
> data structure and bitmask will be used to parse the monitor status
> TLV data in the Rx path.
>
> 1. hal_rx_ppdu_end_user_stats_ext structure
> 2. hal_rx_ppdu_end_duration structure
> 3. HAL_RX_HE_SIG_B2_OFDMA_INFO_INFO0_STA_TXBF bitmask
> 4. HAL_RX_MPDU_START_INFO1_PEERID bitmask
> 5. HAL_INVALID_PEERID
> 6. hal_rx_ppdu_end_user_stats bitmask
>
> Currently, there is no issue since the monitor status Rx path is not
> enabled. However, in the future, the monitor status Rx path will be
> enabled. Therefore, update the above TLV structures and bitmask to align
> with the ath12k 802.11be hardware.
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1
> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
>
> Signed-off-by: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
> Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
Acked-by: Kalle Valo <kvalo@kernel.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-12-17 19:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:45 [PATCH v3 0/8] wifi: ath12k: Refactor the monitor status Rx path Karthikeyan Periyasamy
2024-12-17 8:45 ` [PATCH v3 1/8] wifi: ath12k: Add documentation HTT_H2T_MSG_TYPE_RX_RING_SELECTION_CFG Karthikeyan Periyasamy
2024-12-17 19:46 ` Kalle Valo
2024-12-17 8:45 ` [PATCH v3 2/8] wifi: ath12k: Refactor monitor status TLV structure Karthikeyan Periyasamy
2024-12-17 19:47 ` Kalle Valo [this message]
2024-12-17 8:45 ` [PATCH v3 3/8] wifi: ath12k: cleanup Rx peer statistics structure Karthikeyan Periyasamy
2024-12-17 19:47 ` Kalle Valo
2024-12-17 19:48 ` Kalle Valo
2024-12-17 8:45 ` [PATCH v3 4/8] wifi: ath12k: Fix the misspelled of hal TLV tag HAL_PHYRX_GENERICHT_SIG Karthikeyan Periyasamy
2024-12-17 19:51 ` Kalle Valo
2024-12-17 8:45 ` [PATCH v3 5/8] wifi: ath12k: fix incorrect TID updation in DP monitor status path Karthikeyan Periyasamy
2024-12-17 19:53 ` Kalle Valo
2024-12-17 8:45 ` [PATCH v3 6/8] wifi: ath12k: Remove unused HAL Rx mask in DP monitor path Karthikeyan Periyasamy
2024-12-17 19:54 ` Kalle Valo
2024-12-17 8:45 ` [PATCH v3 7/8] wifi: ath12k: Change the Tx monitor SRNG ring ID Karthikeyan Periyasamy
2024-12-17 19:54 ` Kalle Valo
2024-12-17 8:45 ` [PATCH v3 8/8] wifi: ath12k: Avoid explicit type cast in monitor status parse handler Karthikeyan Periyasamy
2024-12-17 19:55 ` Kalle Valo
2024-12-19 17:54 ` [PATCH v3 0/8] wifi: ath12k: Refactor the monitor status Rx path Jeff Johnson
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=878qseks72.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.