From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Roopni Devanathan <quic_rdevanat@quicinc.com>,
<ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>,
Dinesh Karthikeyan <quic_dinek@quicinc.com>
Subject: Re: [PATCH v4 2/4] wifi: ath12k: Support phy counter and TPC stats
Date: Wed, 6 Nov 2024 16:11:15 -0800 [thread overview]
Message-ID: <c919eed5-e56a-43c2-8a27-cf31673fbf37@quicinc.com> (raw)
In-Reply-To: <20241106044548.3530128-3-quic_rdevanat@quicinc.com>
On 11/5/2024 8:45 PM, Roopni Devanathan wrote:
> From: Dinesh Karthikeyan <quic_dinek@quicinc.com>
>
> Add support to request counters and Transmission Power Control
> (TPC) stats through HTT stats type 37. These stats give
> information about counters like received packet count, CRC pass
> count, error count, transmit abort count, etc., about counter reset
> like reset cause, channel frequency, number and mode, channel flags,
> etc., about TPC like transmit power scale, maximum transmit power,
> gain cap, EIRP, etc.
>
> Note: MCC firmware version -
> WLAN.HMT.1.0-03427-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.15378.4 does not
> support HTT stats type 37, i.e., the firmware does not respond to the
> command requesting stats.
>
> Sample output:
> -------------
> echo 37 > /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_PHY_STATS_TLV:
> bdf_nf_chain[0] = -92
> bdf_nf_chain[1] = -94
> bdf_nf_chain[2] = -94
> bdf_nf_chain[3] = -93
> .....
>
> HTT_PHY_COUNTERS_TLV:
> rx_ofdma_timing_err_cnt = 18068
> rx_cck_fail_cnt = 0
> mactx_abort_cnt = 2612
> macrx_abort_cnt = 0
> .....
>
> HTT_PHY_RESET_STATS_TLV:
> pdev_id = 0
> chan_mhz = 0
> chan_band_center_freq1 = 0
> chan_band_center_freq2 = 0
> .....
>
> HTT_PHY_RESET_COUNTERS_TLV:
> pdev_id = 0
> cf_active_low_fail_cnt = 0
> cf_active_low_pass_cnt = 0
> phy_off_through_vreg_cnt = 0
> .....
>
> HTT_PHY_TPC_STATS_TLV:
> pdev_id = 0
> tx_power_scale = 0
> tx_power_scale_db = 0
> min_negative_tx_power = 0
> .....
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1
>
> Signed-off-by: Dinesh Karthikeyan <quic_dinek@quicinc.com>
> Signed-off-by: Roopni Devanathan <quic_rdevanat@quicinc.com>
Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
next prev parent reply other threads:[~2024-11-07 0:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 4:45 [PATCH v4 0/4] wifi: ath12k: Support Pager, Counter, SoC, Transmit Rate Stats Roopni Devanathan
2024-11-06 4:45 ` [PATCH v4 1/4] wifi: ath12k: Support Downlink Pager Stats Roopni Devanathan
2024-11-07 0:08 ` Jeff Johnson
2024-11-12 15:50 ` Kalle Valo
2024-11-06 4:45 ` [PATCH v4 2/4] wifi: ath12k: Support phy counter and TPC stats Roopni Devanathan
2024-11-07 0:11 ` Jeff Johnson [this message]
2024-11-12 15:52 ` Kalle Valo
2024-11-06 4:45 ` [PATCH v4 3/4] wifi: ath12k: Support SoC Common Stats Roopni Devanathan
2024-11-07 0:12 ` Jeff Johnson
2024-11-06 4:45 ` [PATCH v4 4/4] wifi: ath12k: Support Transmit PER Rate Stats Roopni Devanathan
2024-11-07 0:14 ` Jeff Johnson
2024-11-07 0:15 ` [PATCH v4 0/4] wifi: ath12k: Support Pager, Counter, SoC, Transmit " Jeff Johnson
2024-11-07 19:38 ` Jeff Johnson
2024-11-07 4:40 ` 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=c919eed5-e56a-43c2-8a27-cf31673fbf37@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_dinek@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