From: Sven Eckelmann <sven@narfation.org>
To: Sebastian Gottschall <s.gottschall@newmedia-net.de>
Cc: ath10k@lists.infradead.org, vnaralas@codeaurora.org,
linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] ath10k: provide survey info as accumulated data
Date: Mon, 14 Oct 2019 09:07:42 +0200 [thread overview]
Message-ID: <1614044.H5m0Cyd3Ly@bentobox> (raw)
In-Reply-To: <9a9ec99b-9643-7288-eed5-b549a9fe1487@newmedia-net.de>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On Monday, 14 October 2019 00:15:20 CEST Sebastian Gottschall wrote:
> i checked your patch on 10.4 based chipsets with 9984. the values are
> now looking bogus and wrong at all. busy and active time time in ms does
> increase in hours each second
> the problem seem to be that your patch is 10.2.4 only related.
> ath_clean_survey does not trigger on 10.4 so the values double itself
> each time the event raises since you add the full values and not just a
> delta on top
Thanks for the feedback. So we have now a firmware 10.2.4 which is counting
busy + active up and has wraparound problems. And then we have a 10.4 firmware
(on QCA9888 and QCA4019) which is clearing everything as expected with
WMI_BSS_SURVEY_REQ_TYPE_READ_CLEAR and then we have some 10.4 firmware (one
QCA9984) which behaves more like ath 10.2.4 firmware but is marked as
ATH10K_HW_CC_WRAP_SHIFTED_EACH like the QCA4019.
So I have no idea how to fix this when QCA4019 and QCA9984 are currently
marked the same but behave differently. Does somebody have a overview how the
different HW versions should behave or is there some special bit in the data
reported by the firmware which can be used to evaluate the expected behavior?
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-14 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 12:42 [RFC PATCH 0/2] ath10k: provide survey info as accumulated data Sven Eckelmann
2019-09-18 12:42 ` [RFC PATCH 1/2] ath10k: report survey info as accumulated values Sven Eckelmann
2019-10-11 8:41 ` Kalle Valo
2019-09-18 12:42 ` [RFC PATCH 2/2] ath10k: regularly fetch survey counters Sven Eckelmann
2019-10-11 8:40 ` Kalle Valo
2019-10-11 8:44 ` [RFC PATCH 0/2] ath10k: provide survey info as accumulated data Kalle Valo
2019-10-13 22:15 ` Sebastian Gottschall
2019-10-14 7:07 ` Sven Eckelmann [this message]
2019-10-14 8:57 ` Kalle Valo
2019-10-14 9:32 ` Sebastian Gottschall
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=1614044.H5m0Cyd3Ly@bentobox \
--to=sven@narfation.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@newmedia-net.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).