ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Norik Dzhandzhapanyan <norikd@ethertronics.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] Per chain RSSI reporting
Date: Wed, 31 May 2017 13:05:59 +0000	[thread overview]
Message-ID: <87h901mb1g.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <SN1PR08MB137316C4132262145C58CEA3B0FD0@SN1PR08MB1373.namprd08.prod.outlook.com> (Norik Dzhandzhapanyan's message of "Sat, 27 May 2017 02:09:22 +0000")

Norik Dzhandzhapanyan <norikd@ethertronics.com> writes:

> Inserting the smoothing function here is motivated by what we see as
> 'spikes' in rssi data under weak rssi conditions. Figured its best to
> get rid of the 'bogus' data as close to the source as possible. Also
> to minimize the impact on the changes.
>
> I believe the averaging that happens at higher levels is based on EWMA
> macros in net/mac80211/sta_info.c which not wifi card/chipset
> specific. Didn't want to touch that since other cards seem to not have
> this spikey behavior. And, it doesnt seem to have an effect on the
> ath10k data anyway (iw reports the exact same values for both).
>
> I wonder if it would be acceptable to pass a module load time
> parameter which would indicate an average factor with 0 (as default)
> to indicate no averaging?

I don't know what Johannes thinks, but in my opinion this kind of
smoothing should be in mac80211 and not in drivers. The driver should be
as simple as possible.

-- 
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2017-05-31 13:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 22:49 [PATCH] Per chain RSSI reporting Norik Dzhandzhapanyan
2017-05-27  1:12 ` Adrian Chadd
2017-05-27  2:09   ` Norik Dzhandzhapanyan
2017-05-27  8:30     ` Norik Dzhandzhapanyan
2017-05-27 16:07     ` Ben Greear
2017-05-27 16:39       ` Adrian Chadd
2017-05-27 17:56         ` Michael Ney
2017-05-27 19:30           ` Norik Dzhandzhapanyan
2017-05-27 22:10             ` Michael Ney
2017-05-28  1:22               ` Norik Dzhandzhapanyan
2017-05-27 19:31           ` Norik Dzhandzhapanyan
2017-05-27 19:25         ` Norik Dzhandzhapanyan
2017-05-27 21:38           ` Ben Greear
     [not found]             ` <SN1PR08MB13736CC61B1D00ED2968CF5CB0FD0@SN1PR08MB1373.namprd08.prod.outlook.com>
2017-05-27 21:49               ` Ben Greear
2017-05-30 13:23                 ` Matthias May
2017-05-31 13:05     ` Kalle Valo [this message]
2017-05-31 12:53   ` Kalle Valo
2017-05-31 12:52 ` Kalle Valo

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=87h901mb1g.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=norikd@ethertronics.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