From: Kalle Valo <kvalo@kernel.org>
To: Roopni Devanathan <quic_rdevanat@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
Subject: Re: [PATCH 1/2] wifi: ath12k: Support Transmit Rate Buffer Stats
Date: Tue, 07 Jan 2025 21:41:53 +0200 [thread overview]
Message-ID: <87o70ifm2m.fsf@kernel.org> (raw)
In-Reply-To: <20241128110949.3672364-2-quic_rdevanat@quicinc.com> (Roopni Devanathan's message of "Thu, 28 Nov 2024 16:39:48 +0530")
Roopni Devanathan <quic_rdevanat@quicinc.com> writes:
> From: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
>
> Add support to request transmit rate buffer stats from firmware through
> HTT stats type 31. These stats give information such as MCS, NSS and
> bandwidth of transmit and input buffer.
>
> Sample output:
> -------------
> echo 31 > /sys/kernel/debug/ath12k/pci-0000\:06\:00.0/mac0/htt_stats_type
> cat /sys/kernel/debug/ath12k/pci-0000\:06\:00.0/mac0/htt_stats
> HTT_STATS_PDEV_TX_RATE_TXBF_STATS:
> Legacy OFDM Rates: 6 Mbps: 0, 9 Mbps: 0, 12 Mbps: 0, 18 Mbps: 0
> 24 Mbps: 0, 36 Mbps: 0, 48 Mbps: 0, 54 Mbps: 0
> tx_ol_mcs = 0:0, 1:0, 2:0, 3:0, 4:0, 5:0, 6:0, 7:0, 8:0, 9:0, 10:0, 11:0, 12:0, 13:0
> tx_ibf_mcs = 0:0, 1:0, 2:0, 3:0, 4:0, 5:0, 6:0, 7:0, 8:0, 9:0, 10:0, 11:0, 12:0, 13:0
> tx_txbf_mcs = 0:0, 1:0, 2:0, 3:0, 4:0, 5:0, 6:0, 7:0, 8:0, 9:0, 10:0, 11:0, 12:0, 13:0
> tx_ol_nss = 0:0, 1:0, 2:0, 3:0, 4:0, 5:0, 6:0, 7:0
> tx_ibf_nss = 0:0, 1:0, 2:0, 3:0, 4:0, 5:0, 6:0, 7:0
> tx_txbf_nss = 0:0, 1:0, 2:0, 3:0, 4:0, 5:0, 6:0, 7:0
> tx_ol_bw = 0:0, 1:0, 2:0, 3:0, 4:0
> half_tx_ol_bw = 0:0, 1:0, 2:0, 3:0, 4:0
> quarter_tx_ol_bw = 0:0, 1:0, 2:0, 3:0, 4:0
> tx_ibf_bw = 0:0, 1:0, 2:0, 3:0, 4:0
> half_tx_ibf_bw = 0:0, 1:0, 2:0, 3:0, 4:0
> quarter_tx_ibf_bw = 0:0, 1:0, 2:0, 3:0, 4:0
> tx_txbf_bw = 0:0, 1:0, 2:0, 3:0, 4:0
> half_tx_txbf_bw = 0:0, 1:0, 2:0, 3:0, 4:0
> quarter_tx_txbf_bw = 0:0, 1:0, 2:0, 3:0, 4:0
>
> HTT_STATS_PDEV_TXBF_FLAG_RETURN_STATS:
> TXBF_reason_code_stats: 0:0, 1:0, 2:0, 3:0, 4:0, 5:0, 6:0, 7:0
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.1.1-00214-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: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
> Signed-off-by: Roopni Devanathan <quic_rdevanat@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:[~2025-01-07 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 11:09 [PATCH 0/2] wifi: ath12k: Support Rate and OFDMA Stats Roopni Devanathan
2024-11-28 11:09 ` [PATCH 1/2] wifi: ath12k: Support Transmit Rate Buffer Stats Roopni Devanathan
2024-12-03 0:04 ` Jeff Johnson
2025-01-07 19:41 ` Kalle Valo [this message]
2024-11-28 11:09 ` [PATCH 2/2] wifi: ath12k: Support Transmit Buffer OFDMA Stats Roopni Devanathan
2024-12-03 0:04 ` Jeff Johnson
2025-01-07 19:45 ` Kalle Valo
2025-01-07 23:38 ` Jeff Johnson
2025-01-09 5:38 ` Roopni Devanathan
2025-01-10 20:08 ` Jeff Johnson
2025-01-10 20:17 ` [PATCH 0/2] wifi: ath12k: Support Rate and " 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=87o70ifm2m.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_pradeepc@quicinc.com \
--cc=quic_rdevanat@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;
as well as URLs for NNTP newsgroup(s).