From: Sven Eckelmann <sven@narfation.org>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k@lists.infradead.org, sw@simonwunderlich.de,
vnaralas@codeaurora.org,
Johannes Berg <johannes@sipsolutions.net>,
slakkavalli@datto.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: Add cumulative channel survey dump support.
Date: Wed, 18 Sep 2019 15:07:11 +0200 [thread overview]
Message-ID: <9396620.6V9WzEIOqW@bentobox> (raw)
In-Reply-To: <b24ec622-8510-d8e4-bbc4-86a34c1dd32b@candelatech.com>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On Wednesday, 18 September 2019 14:58:46 CEST Ben Greear wrote:
[...]
> > So as Ben Greear said, the 10.4 firmware version is fixed and 10.2.* (for
> > the wave-1 cards) is still broken and we need a QCA firmware engineer to
> > fix it. Or to work around it by polling every couple of seconds and
> > manually do the cleanup of the values from the firmware.
>
> Have you tried probing very fast, like every 100ms, to see if returned values
> look sane? I seem to recall that there was some firmware issue with this, like
> it only updates internal counters every second or so.
>
> Polling slow would have the same off-by-a-second's-worth-of-data, but you would not
> easily notice it at slower polling intervals.
Yes, I've polled at ~100ms intervals at some point. And it looked like I get
most of the time only 0 values (for everything - including noisefloor) from
the firmware when I do this. And the actual values are only send every second
or so (I didn't actual make precise calculations here).
I have now prepared a test patch [1] to get the data every 10 seconds. This
was a compromise between having useful information over time and the
overflowing problem. While it is not the perfect solution (QCA *cough*), it is
at least more bearable for me.
Kind regards,
Sven
[1] https://patchwork.kernel.org/patch/11150289/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-18 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 9:15 [PATCH] cfg80211: Add cumulative channel survey dump support Venkateswara Naralasetty
2018-05-23 9:54 ` Johannes Berg
2018-05-31 9:06 ` vnaralas
2018-05-31 15:52 ` Ben Greear
2018-06-18 20:46 ` Johannes Berg
2018-06-18 20:57 ` Ben Greear
2018-06-18 20:45 ` Johannes Berg
2019-09-17 17:27 ` Sven Eckelmann
2019-09-17 17:44 ` Ben Greear
2019-09-18 8:46 ` Sven Eckelmann
2019-09-18 12:58 ` Ben Greear
2019-09-18 13:07 ` Sven Eckelmann [this message]
2019-09-18 13:13 ` Sven Eckelmann
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=9396620.6V9WzEIOqW@bentobox \
--to=sven@narfation.org \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=slakkavalli@datto.com \
--cc=sw@simonwunderlich.de \
--cc=vnaralas@codeaurora.org \
/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).