From: Kalle Valo <kvalo@codeaurora.org>
To: Balaji Pothunoori <bpothuno@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] ath10k: average ack rssi support for data frames
Date: Tue, 04 Sep 2018 15:19:22 +0300 [thread overview]
Message-ID: <87va7l78vp.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1536062951-17955-1-git-send-email-bpothuno@codeaurora.org> (Balaji Pothunoori's message of "Tue, 4 Sep 2018 17:39:11 +0530")
Balaji Pothunoori <bpothuno@codeaurora.org> writes:
> Average ack rssi value is weighted average of ack rssi for
> no of msdu's has been sent.
> This feature is enabled by the host driver if firmware is capable.
> After receiving event from host, firmware allocates the necessary
> memory to store the ack_rssi for data packets during the init time.
>
> After each successful transmission, If tx completion status is OK
> and 24th bit is set in HTT message header then host will fetch the
> ack_rssi else host can ignore the ack_rssi field
>
> Signed-off-by: Balaji Pothunoori <bpothuno@codeaurora.org>
> ---
> v2:
> Addressed ath10k-check warnings
> v3:
> cfg80211/mac80211 changes are already merged hence
> rebased ath10k patch alone.
Heh, we had a collision. Just 2 hours ago I rebased v2, fixed some
conflicts and it's now in pending branch:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=ca376d236d335ccc9475ea1ab49df4643d8246b7
So please check that, and if it's good most likely I'll drop this v3.
--
Kalle Valo
next prev parent reply other threads:[~2018-09-04 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 12:09 [PATCH v3] ath10k: average ack rssi support for data frames Balaji Pothunoori
2018-09-04 12:19 ` Kalle Valo [this message]
2018-09-04 12:36 ` Balaji Pothunoori
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=87va7l78vp.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=bpothuno@codeaurora.org \
--cc=linux-wireless@vger.kernel.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