From: Ben Greear <greearb@candelatech.com>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: Fix getting stats from firmware.
Date: Fri, 21 Mar 2014 11:51:30 -0700 [thread overview]
Message-ID: <532C8A32.70501@candelatech.com> (raw)
In-Reply-To: <CAEFj985bx2ZK-Y08yrJirqNhBQFt_CF_1hGPaj_qTRSvnU4DJw@mail.gmail.com>
On 03/21/2014 09:48 AM, Yeoh Chun-Yeow wrote:
>> I did a quick check again on STA mode. With or without your patch, the
>> printed peer stats are both identical but both wrong. See below:
>>
>> ath10k PEER stats
>> =================
>>
>> Peer MAC address 00:00:00:00:00:00
>> Peer RSSI 256
>> Peer TX rate 0
>>
>> Peer MAC address 00:00:00:00:04:f0
>> Peer RSSI 17317
>> Peer TX rate 73
>>
>> So I think that your patch makes no difference but do indeed providing
>> "correct" peer stats on latest AP firmware.
It looks like the peer stats are broken on my 10.x firmware as well. Other pdev tx/rx
stats look like they are at least possibly correct.
Since ath10k supports more than one vdev, we also will want to extend it to
get peer for the rest of the vdevs some day.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-03-21 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 0:05 [PATCH] ath10k: Fix getting stats from firmware greearb
2014-03-21 6:33 ` Michal Kazior
2014-03-21 6:41 ` Yeoh Chun-Yeow
2014-03-21 16:03 ` Ben Greear
2014-03-21 16:12 ` Kalle Valo
2014-03-21 16:42 ` Yeoh Chun-Yeow
2014-03-21 16:48 ` Yeoh Chun-Yeow
2014-03-21 18:51 ` Ben Greear [this message]
2014-03-21 17:29 ` Ben Greear
2014-03-21 15:56 ` Ben Greear
2014-03-21 16:09 ` Kalle Valo
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=532C8A32.70501@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=yeohchunyeow@gmail.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;
as well as URLs for NNTP newsgroup(s).