From: Anilkumar Kolli <akolli@codeaurora.org>
To: ath11k@lists.infradead.org
Subject: [PATCH] ath11k: mac: Remove WAR on max a-mpdu len in vht
Date: Tue, 29 Oct 2019 12:30:56 +0530 [thread overview]
Message-ID: <1572332456-5419-1-git-send-email-akolli@codeaurora.org> (raw)
Revert commit a24b88b56074424a413a ("ath10k: Fix bug in max.
VHT A-MPDU size"), Moving this logic to mac80211.
Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org>
---
drivers/net/wireless/ath/ath11k/mac.c | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/net/wireless/ath/ath11k/mac.c b/drivers/net/wireless/ath/ath11k/mac.c
index d2a4bae6e057..2c9f57e741c3 100644
--- a/drivers/net/wireless/ath/ath11k/mac.c
+++ b/drivers/net/wireless/ath/ath11k/mac.c
@@ -1041,14 +1041,7 @@ static void ath11k_peer_assoc_h_vht(struct ath11k *ar,
IEEE80211_VHT_CAP_MAX_A_MPDU_LENGTH_EXPONENT_MASK) >>
IEEE80211_VHT_CAP_MAX_A_MPDU_LENGTH_EXPONENT_SHIFT;
- /* Workaround: Some Netgear/Linksys 11ac APs set Rx A-MPDU factor to
- * zero in VHT IE. Using it would result in degraded throughput.
- * arg->peer_max_mpdu at this point contains HT max_mpdu so keep
- * it if VHT max_mpdu is smaller.
- */
- arg->peer_max_mpdu = max(arg->peer_max_mpdu,
- (1U << (IEEE80211_HT_MAX_AMPDU_FACTOR +
- ampdu_factor)) - 1);
+ arg->peer_max_mpdu = BIT(IEEE80211_HT_MAX_AMPDU_FACTOR + ampdu_factor) - 1;
if (sta->bandwidth == IEEE80211_STA_RX_BW_80)
arg->bw_80 = true;
--
1.9.1
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next reply other threads:[~2019-10-29 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 7:00 Anilkumar Kolli [this message]
2019-10-30 14:52 ` [PATCH] ath11k: mac: Remove WAR on max a-mpdu len in vht 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=1572332456-5419-1-git-send-email-akolli@codeaurora.org \
--to=akolli@codeaurora.org \
--cc=ath11k@lists.infradead.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