From: Ben Greear <greearb@candelatech.com>
To: Sven Eckelmann <sven@narfation.org>,
vnaralas@codeaurora.org, ath10k@lists.infradead.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, sw@simonwunderlich.de,
slakkavalli@datto.com
Subject: Re: [PATCH] cfg80211: Add cumulative channel survey dump support.
Date: Tue, 17 Sep 2019 10:44:03 -0700 [thread overview]
Message-ID: <cc8bc245-034b-376d-3952-0c0ac6d51cab@candelatech.com> (raw)
In-Reply-To: <2083094.mFhUXK7yzB@bentobox>
On 9/17/19 10:27 AM, Sven Eckelmann wrote:
> On Thursday, 31 May 2018 11:06:59 CEST vnaralas@codeaurora.org wrote:
>> I will sent next version of patch with updated commit log.
>
> Can you please point me to the second version?
>
> Btw. I've just checked the minimal changes in ath10k to get this working. It
> seems we need SURVEY_INFO_NON_ACC_DATA in ath10k's ath10k_get_survey + memset
> of ar->survey[idx].
>
> But right now the total time looks (especially) wrong to me. At least it is
> rather unlikely that I can have around 30 second active time delta in
> roughly 1 real world second. Maybe a bug with the READ_CLEAR handling in
> firmware 10.2.4-1.0-00043 or maybe all firmware version? More logs about
> that at the end.
>
> @Ben: Was this also what you've experience in the past with the 10.2 firmware
> bss_chan_info counter bugs or am I just misusing the functionality of the
> firmware?
Last I recall, the upstream code had several bugs. Maybe some QCA
firmware person can let you know if they fixed the upstream firmware.
If you want to test against ath10k-ct driver/firmware, and if you still see bogus values, then
I can debug and fix it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2019-09-17 17:44 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 [this message]
2019-09-18 8:46 ` Sven Eckelmann
2019-09-18 12:58 ` Ben Greear
2019-09-18 13:07 ` Sven Eckelmann
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=cc8bc245-034b-376d-3952-0c0ac6d51cab@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=slakkavalli@datto.com \
--cc=sven@narfation.org \
--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).