linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* ath10k: fw_stats not reporting peer_stats with 10.2
@ 2014-12-18 13:00 Antonio Quartulli
  2015-01-12 11:54 ` Michal Kazior
  0 siblings, 1 reply; 3+ messages in thread
From: Antonio Quartulli @ 2014-12-18 13:00 UTC (permalink / raw)
  To: ath10k; +Cc: linux-wireless

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

Hello,

I have a device equipped with a ath10k driven wifi card, specifically:

qca988x hw2.0 (0x4100016c, 0x043202ff) fw 10.2-00082-4-2 api 3 htt 2.1
wmi 65.109.0.0 cal file


(line grabbed from dmesg at boot time)

On my device I have configured 2 AP vifs and for each of them I would
like to read the last TX rate of the associated stations.

As I've read on wireless.kernel.org this is not possible through the
standard nl/cfg80211 interface and therefore I have been trying to read
/sys/kernel/debug/ieee80211/phy1/ath10k/fw_stats  , but this file always
reports "ath10k PEER stats (0)" (no peers..).

I tried printing some debug messages here and there and the only useful
information I got is that in "ath10k_wmi_10x_pull_fw_stats()" the value
of "ev->num_peer_stats" is always 0.

Is this yet another fw limitation?


I also realized that upon station connection ath10k receives the
WMI_10_2_PEER_RATECODE_LIST_EVENTID event but it is not handled as no
handler is implemented. Might it be related with my problem ?


Thanks a lot for any information you would be able to provide :)

Cheers,


-- 
Antonio Quartulli


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-01-13  7:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-18 13:00 ath10k: fw_stats not reporting peer_stats with 10.2 Antonio Quartulli
2015-01-12 11:54 ` Michal Kazior
2015-01-13  7:11   ` Antonio Quartulli

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).