From: Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com>
To: Roopni Devanathan <quic_rdevanat@quicinc.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
Sowmiya Sree Elavalagan <quic_ssreeela@quicinc.com>,
Ramya Gnanasekar <quic_rgnanase@quicinc.com>
Subject: Re: [PATCH v6 2/2] wifi: ath12k: Add Support to Calculate and Display TPC Values
Date: Mon, 3 Feb 2025 20:48:35 +0530 [thread overview]
Message-ID: <14f4fcc5-b39e-495e-bdee-ef37fcca2d32@oss.qualcomm.com> (raw)
In-Reply-To: <20250130061104.962124-3-quic_rdevanat@quicinc.com>
On 1/30/25 11:41, Roopni Devanathan wrote:
> From: Sowmiya Sree Elavalagan<quic_ssreeela@quicinc.com>
>
> Transmit Power Control(TPC) stats should display per chain TPC value per
> radio. Add debugfs support to read and display TPC stats type and TPC
> stats. Take power values for each preamble type, rate and NSS combination
> from a particular index from each power arrays based on number of chains,
> NSS, modes, MCS and tx beamforming enabled/disabled parameters. Minimum
> of the values taken from reg power table, rates and Conformance Test
> Limit(CTL) array table should give the TPC which is in 0.25 dBm steps.
>
> Sample Output:
> -------------
> echo 1 > /sys/kernel/debug/ath12k/pci-0000\:06\:00.0/mac0/tpc_stats_type
> cat /sys/kernel/debug/ath12k/pci-0000\:06\:00.0/mac0/tpc_stats
>
> *************** TPC config **************
> * powers are in 0.25 dBm steps
> reg domain-22 chan freq-5955
> power limit-126 max reg-domain Power-252
> No.of tx chain-4 No.of rates-1164
> **************** SU WITH TXBF ****************
> TPC values for Active chains
> Rate idx Preamble Rate code 1-Chain 2-Chain 3-Chain 4-Chain
> 4 OFDM 0x000 39 15 1 -9
> 5 OFDM 0x001 39 15 1 -9
> .....
> 12 HT20 0x200 40 16 2 -8
> 13 HT20 0x201 40 16 2 -8
> .....
> 44 HT40 0x200 88 88 88 88
> 45 HT40 0x201 88 88 88 88
> .....
> 76 VHT20 0x300 40 16 2 -8
> 77 VHT20 0x301 40 16 2 -8
> .....
> 172 VHT40 0x300 88 88 88 88
> 173 VHT40 0x301 88 88 88 88
> .....
> 412 HE20 0x400 88 88 88 88
> 413 HE20 0x401 88 88 88 88
> .....
> 508 HE40 0x400 76 76 76 76
> 509 HE40 0x401 76 76 76 76
> .....
> 748 EHT20 0x50e 88 88 88 88
> 749 EHT20 0x50f 88 88 88 88
> .....
> 812 EHT40 0x50e 88 88 88 88
> 813 EHT40 0x50f 88 88 88 88
> .....
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.1.1-00214-QCAHKSWPL_SILICONZ-1
>
> Signed-off-by: Sowmiya Sree Elavalagan<quic_ssreeela@quicinc.com>
> Co-developed-by: Ramya Gnanasekar<quic_rgnanase@quicinc.com>
> Signed-off-by: Ramya Gnanasekar<quic_rgnanase@quicinc.com>
> Co-developed-by: Roopni Devanathan<quic_rdevanat@quicinc.com>
> Signed-off-by: Roopni Devanathan<quic_rdevanat@quicinc.com>
> ---
Reviewed-by: Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com>
--
Aditya
next prev parent reply other threads:[~2025-02-03 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 6:11 [PATCH v6 0/2] wifi: ath12k: Support Transmit Power Control Stats Roopni Devanathan
2025-01-30 6:11 ` [PATCH v6 1/2] wifi: ath12k: Add Support to Parse TPC Event from Firmware Roopni Devanathan
2025-02-03 15:15 ` Aditya Kumar Singh
2025-01-30 6:11 ` [PATCH v6 2/2] wifi: ath12k: Add Support to Calculate and Display TPC Values Roopni Devanathan
2025-02-03 15:18 ` Aditya Kumar Singh [this message]
2025-02-04 1:13 ` [PATCH v6 0/2] wifi: ath12k: Support Transmit Power Control Stats 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=14f4fcc5-b39e-495e-bdee-ef37fcca2d32@oss.qualcomm.com \
--to=aditya.kumar.singh@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rdevanat@quicinc.com \
--cc=quic_rgnanase@quicinc.com \
--cc=quic_ssreeela@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