All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Thirumalai <tpachamu@qca.qualcomm.com>,
	<linux-wireless@vger.kernel.org>,
	ath6kl-devel <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH 0/4] Enable uAPSD support in AP mode
Date: Mon, 9 Jan 2012 13:46:41 +0200	[thread overview]
Message-ID: <4F0AD3A1.5020100@qca.qualcomm.com> (raw)
In-Reply-To: <1326099268.3451.0.camel@jlt3.sipsolutions.net>

On 01/09/2012 10:54 AM, Johannes Berg wrote:
> On Mon, 2012-01-09 at 13:14 +0530, Thirumalai wrote:
>> In addition to legacy power save, this series of patch adds
>> support for uAPSD in AP mode.
>>
>> When connected station goes into suspend state, the driver will
>> start queuing pkts in the separate queue (called uapsd queue)
>> until the station ask for it. 
>>
>> The moment driver starting queuing, it will enable traffic indication
>> bit for the client connected to indicate data availability. 
>> Once station ask for the data (via Trigger frame), the driver will 
>> dequeue and send pkt one by one to the station.
> 
> The way you describe this sounds incorrect, but I'll leave it to Kalle
> to figure out what you're doing and whether it is correct or not ... if
> only some ACs are trigger-enabled those don't influence the TIM bit.

Yeah, that does sound odd. Thirumalai, does the code really this way or
is it just a problem with the description? (I need to study the code in
detail still.)

Johannes, thanks for pointing this out.

Kalle

  reply	other threads:[~2012-01-09 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  7:44 [PATCH 0/4] Enable uAPSD support in AP mode Thirumalai
2012-01-09  8:54 ` Johannes Berg
2012-01-09 11:46   ` Kalle Valo [this message]
2012-01-10 17:38     ` Pachamuthu, Thirumalai
2012-01-09 11:37 ` 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=4F0AD3A1.5020100@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tpachamu@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.