From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] ath10k: Fix invalid survey reporting for QCA99X0
Date: Mon, 17 Aug 2015 16:46:53 +0300 [thread overview]
Message-ID: <87twrydo36.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1439376845-17245-1-git-send-email-vthiagar@qti.qualcomm.com> (Vasanthakumar Thiagarajan's message of "Wed, 12 Aug 2015 16:24:04 +0530")
Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> writes:
> There are three WMI_CHAN_INFO events reported per channel
> in QCA99X0 firmware. First one is a notification at the begining
> of the channel dwell time with cmd_flag as CHAN_INFO_START(cmd_flag = 0),
> second one is a notification at the end of the dwell time with cmd_flag
> CHAN_INFO_PRE_COMPLETE (cmd_flag = 2) and the third is the indication
> with CHAN_INFO_COMPLETE (cmd_flag = 1) which is the last indication for
> the channel. Since there is a new state before the completion, the handler
> is to fixed so that the counts are deducted from the ones reported with
> CHAN_INFO_START rather than the ones reported with CHAN_INFO_PRE_COMPLETE.
> Without this fix there will be lots of 0 msecs reported as active
> and busy time.
>
> Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Thanks, both applied.
--
Kalle Valo
prev parent reply other threads:[~2015-08-17 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 10:54 [PATCH 1/2] ath10k: Fix invalid survey reporting for QCA99X0 Vasanthakumar Thiagarajan
2015-08-12 10:54 ` [PATCH 2/2] ath10k: Add cycle/rx_clear counters frequency to hw_params Vasanthakumar Thiagarajan
2015-08-17 13:46 ` Kalle Valo [this message]
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=87twrydo36.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vthiagar@qti.qualcomm.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).