From: Felix Fietkau <nbd@openwrt.org>
To: Sujith Manoharan <sujith@msujith.org>,
John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com
Subject: Re: [PATCH 1/4] ath9k: Fix channel context transition
Date: Wed, 27 Aug 2014 10:38:39 +0200 [thread overview]
Message-ID: <53FD990F.8050606@openwrt.org> (raw)
In-Reply-To: <1409121445-11484-2-git-send-email-sujith@msujith.org>
On 2014-08-27 08:37, Sujith Manoharan wrote:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> In channel context mode, a nullfunc is sent with
> the PM bit enabled when we switch to a new channel
> context from the current one. But, when the scheduler
> switches back to the old context, sending a nullfunc
> with PM bit cleared has to be done only if there is
> buffered traffic at the AP.
>
> Currently, this is not done and a nullfunc is sent
> for every transition. Fix this by parsing the TIM IE
> for a received beacon and checking if there is buffered
> traffic.
That does not make much sense to me. Why would you not inform the AP and
instead let it start buffering until the next beacon period?
- Felix
next prev parent reply other threads:[~2014-08-27 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 6:37 [PATCH 0/4] ath9k patches Sujith Manoharan
2014-08-27 6:37 ` [PATCH 1/4] ath9k: Fix channel context transition Sujith Manoharan
2014-08-27 8:38 ` Felix Fietkau [this message]
2014-08-27 9:55 ` Sujith Manoharan
2014-08-27 10:40 ` Jouni Malinen
2014-08-27 10:46 ` Sujith Manoharan
2014-08-27 6:37 ` [PATCH 2/4] ath9k: Disable fastcc for channel context mode Sujith Manoharan
2014-08-27 8:39 ` Felix Fietkau
2014-08-27 9:58 ` Sujith Manoharan
2014-08-27 6:37 ` [PATCH 3/4] ath9k: Add more debug statements for channel context Sujith Manoharan
2014-08-27 6:37 ` [PATCH 4/4] ath9k: Fix channel context timer Sujith Manoharan
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=53FD990F.8050606@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@qca.qualcomm.com \
--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 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.