public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Nicolas Escande <nico.escande@gmail.com>,
	Sowmiya Sree Elavalagan <quic_ssreeela@quicinc.com>,
	ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
	Sivashankari Madhavan <quic_sivamadh@quicinc.com>
Subject: Re: [PATCH ath-next v2] wifi: ath12k: support average ack rssi in station dump
Date: Mon, 7 Jul 2025 12:05:14 -0700	[thread overview]
Message-ID: <10d52ab4-a0cd-445f-a23d-9396904b10df@oss.qualcomm.com> (raw)
In-Reply-To: <DAKJLG9RLFCQ.3H8XQHL8ZY3GT@gmail.com>

On 6/12/2025 5:10 AM, Nicolas Escande wrote:
> On Thu Jun 12, 2025 at 1:46 PM CEST, Sowmiya Sree Elavalagan wrote:
>> From: Sivashankari Madhavan <quic_sivamadh@quicinc.com>
>>
>> Currently, the ACK RSSI value is not shown in station dump. Enable WMI
>> resource flag for ACK RSSI in WMI INIT command to add ACK RSSI value in
>> management TX completion event from WMI. Update ACK RSSI value obtained
>> in management and data frame completion path to ieee80211_tx_info. Also
>> advertise NL80211_EXT_FEATURE_ACK_SIGNAL_SUPPORT flag during hardware
>> register to mac80211 layer so that ACK RSSI is added to station dump
>> message.
>>
>> Example output :
>> Station 00:03:7f:01:5c:4b (on wlp88s0)
>>         inactive time:  46584 ms
>>         rx bytes:       955
>>         rx packets:     10
>>         tx bytes:       769
>>         tx packets:     6
>>         tx retries:     81
>>         tx failed:      0
>>         rx drop misc:   0
>>         signal:         -39 dBm
>>         signal avg:     -40 dBm
>>         tx bitrate:     6.0 MBit/s
>>         tx duration:    1185 us
>>         rx bitrate:     309.7 MBit/s 40MHz HE-MCS 6 HE-NSS 2 HE-GI 0 HE-DCM 0
>>         rx duration:    0 us
>>         last ack signal:-41 dBm
>>         avg ack signal: -40 dBm
>>         authorized:     yes
>>         authenticated:  yes
>> 	.......
>>
>> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-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: Sivashankari Madhavan <quic_sivamadh@quicinc.com>
>> Signed-off-by: Sowmiya Sree Elavalagan <quic_ssreeela@quicinc.com>
> [...]
>> @@ -5651,6 +5655,8 @@ static int ath12k_pull_mgmt_tx_compl_param_tlv(struct ath12k_base *ab,
>>  	param->pdev_id = ev->pdev_id;
>>  	param->desc_id = ev->desc_id;
>>  	param->status = ev->status;
>> +	param->ppdu_id = ev->ppdu_id;
> Hello,
> It seems this ppdu_id is retrieved from frimware but not used in this patchset
> Is this by design ?

I'm guessing it is for completeness (parse all members even if they aren't
used). Do you think this is a problem?

/jeff


  reply	other threads:[~2025-07-07 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 11:46 [PATCH ath-next v2] wifi: ath12k: support average ack rssi in station dump Sowmiya Sree Elavalagan
2025-06-12 12:10 ` Nicolas Escande
2025-07-07 19:05   ` Jeff Johnson [this message]
2025-07-08  7:36     ` Nicolas Escande
2025-07-08 16:09 ` 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=10d52ab4-a0cd-445f-a23d-9396904b10df@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nico.escande@gmail.com \
    --cc=quic_sivamadh@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