linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janusz Dziedzic <janusz.dziedzic@tieto.com>
To: linux-wireless@vger.kernel.org
Cc: ath9k-devel@lists.ath9k.org, nbd@openwrt.org,
	Janusz Dziedzic <janusz.dziedzic@tieto.com>
Subject: [PATCH v2 03/13] ath9k: queue null frames in case of MCC
Date: Fri, 27 Nov 2015 09:37:08 +0100	[thread overview]
Message-ID: <1448613438-5173-3-git-send-email-janusz.dziedzic@tieto.com> (raw)
In-Reply-To: <1448613438-5173-1-git-send-email-janusz.dziedzic@tieto.com>

While mac80211 using null frames when connection polling,
we should queue this frames while NOA could be there, and
AP, P2P_GO could be not present.

Without this patch, with no traffic we often saw disconnections
while we try to send nullfunc when AP/GO wasn't present.

Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
---
 drivers/net/wireless/ath/ath9k/xmit.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c
index 26698a6..82fc76f 100644
--- a/drivers/net/wireless/ath/ath9k/xmit.c
+++ b/drivers/net/wireless/ath/ath9k/xmit.c
@@ -2331,6 +2331,12 @@ int ath_tx_start(struct ieee80211_hw *hw, struct sk_buff *skb,
 
 	queue = ieee80211_is_data_present(hdr->frame_control);
 
+	/* If chanctx, queue all null frames while NOA could be there */
+	if (ath9k_is_chanctx_enabled() &&
+	    ieee80211_is_nullfunc(hdr->frame_control) &&
+	    !txctl->force_channel)
+		queue = true;
+
 	/* Force queueing of all frames that belong to a virtual interface on
 	 * a different channel context, to ensure that they are sent on the
 	 * correct channel.
-- 
1.9.1


  parent reply	other threads:[~2015-11-27  8:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27  8:37 [PATCH v2 01/13] ath9k: add debug messages to aggr/chanctx funcs Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 02/13] ath9k: print real timer value Janusz Dziedzic
2015-11-27  8:37 ` Janusz Dziedzic [this message]
2015-11-27  8:37 ` [PATCH v2 04/13] ath9k: P2P_CLIENT, send frames after 1ms AP/GO will aprear Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 05/13] ath9k: use u32 when calculate tsf Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 06/13] ath9k: setup correct skb priority for nullfunc Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 07/13] ath9k: MCC enable Opportunistic Power Save Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 08/13] ath9k: P2P_CLIENT, get/set NOA correctly Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 09/13] ath9k: request NOA update when chanctx active Janusz Dziedzic
2015-12-01 13:13   ` Kalle Valo
2016-01-28  8:21   ` Kalle Valo
2015-11-27  8:37 ` [PATCH v2 10/13] ath9k: MCC, add NOA also in case of an AP Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 11/13] ath9k: MCC add sta_ap_ratio module param Janusz Dziedzic
2015-12-11  8:19   ` Kalle Valo
2015-12-17  9:44     ` Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 12/13] ath9k: MCC, print time elapsed between events Janusz Dziedzic
2015-11-27  8:37 ` [PATCH v2 13/13] ath9k: remove ath9k_mod_tsf64_tu Janusz Dziedzic
2015-12-08 15:03 ` [PATCH v2 01/13] ath9k: add debug messages to aggr/chanctx funcs 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=1448613438-5173-3-git-send-email-janusz.dziedzic@tieto.com \
    --to=janusz.dziedzic@tieto.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.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).