From: Felix Fietkau <nbd@openwrt.org>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH 2/2] ath9k_hw: tweak noise immunity thresholds for older chipsets
Date: Fri, 28 Feb 2014 21:54:11 +0100 [thread overview]
Message-ID: <5310F773.3000405@openwrt.org> (raw)
In-Reply-To: <21264.56017.114049.511221@gargle.gargle.HOWL>
On 2014-02-28 19:52, Sujith Manoharan wrote:
> Felix Fietkau wrote:
>> Older chipsets are more sensitive to high PHY error counts, and the
>> current noise immunity thresholds were based on tests run at QCA with
>> newer chipsets.
>>
>> This patch brings back the values from the old ANI implementation for
>> old chipsets, and it also disables weak signal detection on an earlier
>> noise immunity level, to improve overall radio stability on affected
>> devices.
>
> Which devices ?
Reproduced on AR913x, suspected on AR928x, probably other affected
devices as well.
> Since the old values were used in the old ANI implementation, I am not sure
> how just retrofitting them into the new ANI algorithm can improve things...
Semantically, the values are compatible. The algorithm is similar enough
that this works just fine. The patch has gone through some testing that
showed a visible stability improvement.
- Felix
next prev parent reply other threads:[~2014-02-28 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 18:02 [PATCH 1/2] ath9k_hw: toggle weak signal detection in AP mode on older chipsets Felix Fietkau
2014-02-28 18:02 ` [PATCH 2/2] ath9k_hw: tweak noise immunity thresholds for " Felix Fietkau
2014-02-28 18:52 ` Sujith Manoharan
2014-02-28 20:54 ` Felix Fietkau [this message]
2014-02-28 18:43 ` [PATCH 1/2] ath9k_hw: toggle weak signal detection in AP mode on " Sujith Manoharan
2014-02-28 20:52 ` Felix Fietkau
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=5310F773.3000405@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sujith@msujith.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).