From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Ramya Gnanasekar <quic_rgnanase@quicinc.com>,
<ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v5 4/4] wifi: ath12k: Dump additional Tx PDEV HTT stats
Date: Mon, 17 Jun 2024 13:45:22 -0700 [thread overview]
Message-ID: <cd8c0d02-4175-4eea-b4c2-e4cd6250071f@quicinc.com> (raw)
In-Reply-To: <20240614063404.2659089-5-quic_rgnanase@quicinc.com>
On 6/13/2024 11:34 PM, Ramya Gnanasekar wrote:
> Support to dump additional Tx PDEV stats through HTT stats debugfs.
> Following stats dump are supported:
> 1. PDEV control path stat to dump Tx management frame count
> 2. Tx PDEV SIFS histogram stats
> 3. Tx MU MIMO PPDU stats for 802.11ac, 802.11ax and 802.11be
>
> Sample Output:
> ---------------
> echo 1 > /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
>
...
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-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: Ramya Gnanasekar <quic_rgnanase@quicinc.com>
Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
prev parent reply other threads:[~2024-06-17 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 6:34 [PATCH v5 0/4] wifi: ath12k: Add support to enable debugfs_htt_stats Ramya Gnanasekar
2024-06-14 6:34 ` [PATCH v5 1/4] " Ramya Gnanasekar
2024-06-17 20:45 ` Jeff Johnson
2024-06-14 6:34 ` [PATCH v5 2/4] wifi: ath12k: Add htt_stats_dump file ops support Ramya Gnanasekar
2024-06-17 20:45 ` Jeff Johnson
2024-06-14 6:34 ` [PATCH v5 3/4] wifi: ath12k: Add support to parse requested stats_type Ramya Gnanasekar
2024-06-17 20:45 ` Jeff Johnson
2024-06-14 6:34 ` [PATCH v5 4/4] wifi: ath12k: Dump additional Tx PDEV HTT stats Ramya Gnanasekar
2024-06-17 20:45 ` 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=cd8c0d02-4175-4eea-b4c2-e4cd6250071f@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rgnanase@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