All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Vasanthakumar Thiagarajan <vthiagar@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH V2] ath11k: Fix Rx signal strength reporting
Date: Thu, 20 Jun 2019 13:36:50 +0000 (UTC)	[thread overview]
Message-ID: <20190620133651.58CC76016D@smtp.codeaurora.org> (raw)
In-Reply-To: <1560399999-14062-1-git-send-email-vthiagar@codeaurora.org>

Vasanthakumar Thiagarajan <vthiagar@codeaurora.org> wrote:

> Since rssi in not reported in MSDU_START tlv, current signal strength
> reporting is always wrong. Correct rssi is reported in PPDU_END tlv.
> Enable PPDU_END, PPDU_END_STATUS_DONE and MPDU_START tlv reporting in
> monitor status by default. Pass the sta's Rx signal strength to mac80211
> in sta_statistics() ops. This patch also makes sure the default rx filter
> is always enabled whenever there is a call to reset the filter (from
> extd_rx_stats debugfs and config_filter path). Since some of the rx_stats
> are enabled by default, make memory allocation of arsta->rx_stats unconditional.
> 
> Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

Patch applied to ath11k-bringup branch of ath.git, thanks.

ecdb3adeda5c ath11k: Fix Rx signal strength reporting

-- 
https://patchwork.kernel.org/patch/10991095/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

      parent reply	other threads:[~2019-06-20 13:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13  4:26 [PATCH V2] ath11k: Fix Rx signal strength reporting Vasanthakumar Thiagarajan
2019-06-17 15:31 ` Kalle Valo
2019-06-17 15:33   ` Kalle Valo
2019-06-17 15:54     ` Vasanthakumar Thiagarajan
2019-06-20 13:36     ` Kalle Valo
2019-06-20 13:36 ` 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=20190620133651.58CC76016D@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=vthiagar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.