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 3/3] ath10k: average ack rssi support for data frames
Date: Fri, 13 Apr 2018 16:56:45 +0300 [thread overview]
Message-ID: <87efjjqkf6.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1523619357-1963-4-git-send-email-bpothuno@codeaurora.org> (Balaji Pothunoori's message of "Fri, 13 Apr 2018 17:05:57 +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.
>
> Note: This patch is depends on cfg80211 patch.
>
> Signed-off-by: Balaji Pothunoori <bpothuno@codeaurora.org>
> ---
> drivers/net/wireless/ath/ath10k/core.c | 4 ++++
> drivers/net/wireless/ath/ath10k/htt.h | 6 +++++-
> drivers/net/wireless/ath/ath10k/htt_rx.c | 21 +++++++++++++++++++++
> drivers/net/wireless/ath/ath10k/mac.c | 4 ++++
> drivers/net/wireless/ath/ath10k/wmi.h | 8 ++++++++
> 5 files changed, 42 insertions(+), 1 deletion(-)
Usually notes like above are better to put under "---" line, this way
git-am will not include in the git commit log.
--
Kalle Valo
next prev parent reply other threads:[~2018-04-13 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 11:35 [PATCH 3/3] ath10k: average ack rssi support for data frames Balaji Pothunoori
2018-04-13 13:56 ` Kalle Valo [this message]
2018-04-14 6:44 ` kbuild test robot
2018-04-14 6:56 ` kbuild test robot
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=87efjjqkf6.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;
as well as URLs for NNTP newsgroup(s).