From: Felix Fietkau <nbd@openwrt.org>
To: "Martin Hundebøll" <m.hundeboll@gmail.com>
Cc: Seth Forshee <seth.forshee@canonical.com>,
linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>,
Jouni Malinen <jouni@qca.qualcomm.com>,
Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>,
Senthil Balasubramanian <senthilb@qca.qualcomm.com>
Subject: Re: CTS timeout issue with AR9285
Date: Thu, 02 Feb 2012 15:22:30 +0100 [thread overview]
Message-ID: <4F2A9C26.5070201@openwrt.org> (raw)
In-Reply-To: <4F2A9A9D.4000108@gmail.com>
On 2012-02-02 3:15 PM, Martin Hundebøll wrote:
> Hi Felix,
>
> On 2012-02-02 13:35, Felix Fietkau wrote:
>> Please try this patch:
>>
>> --- a/drivers/net/wireless/ath/ath9k/hw.c
>> +++ b/drivers/net/wireless/ath/ath9k/hw.c
>> @@ -1061,13 +1061,16 @@ void ath9k_hw_init_global_settings(struc
>>
>> /*
>> * Workaround for early ACK timeouts, add an offset to match the
>> - * initval's 64us ack timeout value.
>> + * initval's 64us ack timeout value. Use 48us for the CTS timeout.
>> * This was initially only meant to work around an issue with delayed
>> * BA frames in some implementations, but it has been found to fix ACK
>> * timeout issues in other cases as well.
>> */
>> - if (conf->channel&& conf->channel->band == IEEE80211_BAND_2GHZ)
>> + if (conf->channel&& conf->channel->band == IEEE80211_BAND_2GHZ) {
>> acktimeout += 64 - sifstime - ah->slottime;
>> + ctstimeout += 48 - sifstime - ah->slottime;
>> + }
>> +
>>
>> ath9k_hw_set_sifs_time(ah, sifstime);
>> ath9k_hw_setslottime(ah, slottime);
>
> I have been seeing the same issues with the Atheros 9170 USB chipset
> using the carl9170 driver and firmware, where RST are transmitted
> repeatidly, even though a CTS-reply is seen on the air. I suspect the
> issue to be related to this one, but I am unable to locate any
> calculation or setting of CTS timeout in the driver or firmware.
>
> Can anyone point me in the right direction to tune the CTS timeout
> with the 9170 chip?
I think your carl9170 CTS issue is likely to be something else, since
AR9170 is using a completely different 802.11 MAC (Zydas design instead
of Atheros).
- Felix
next prev parent reply other threads:[~2012-02-02 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 4:25 CTS timeout issue with AR9285 Seth Forshee
2012-02-02 11:28 ` Mohammed Shafi
2012-02-02 14:20 ` Seth Forshee
2012-02-02 12:35 ` Felix Fietkau
2012-02-02 14:15 ` Martin Hundebøll
2012-02-02 14:22 ` Felix Fietkau [this message]
2012-02-02 14:38 ` Seth Forshee
2012-02-04 6:08 ` Marek Lindner
2012-02-04 10:24 ` Adrian Chadd
2012-02-04 20:18 ` 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=4F2A9C26.5070201@openwrt.org \
--to=nbd@openwrt.org \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=m.hundeboll@gmail.com \
--cc=mcgrof@qca.qualcomm.com \
--cc=senthilb@qca.qualcomm.com \
--cc=seth.forshee@canonical.com \
--cc=vthiagar@qca.qualcomm.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 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.