Linux wireless drivers development
 help / color / mirror / Atom feed
From: <vivekanandah@posedge.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	<linux-wireless@vger.kernel.org>
Subject: Re: question on SMPS for AP
Date: Wed, 3 Apr 2013 01:37:30 -0700	[thread overview]
Message-ID: <8a7f0b7f3bc246cc8bacb37f4717b254@posedge.com> (raw)
In-Reply-To: <CAGXE3d_Up9BwfR3gC4uDh_4PNfAaMCME7dVeRnNrpmvc70ZALQ@mail.gmail.com>

Hi helmut,

thanks for the response.

thanks and regards
Vivek


On Wed, 3 Apr 2013 10:09:51 +0200, Helmut Schaa wrote:
> Hi Vivek,
>
> On Wed, Apr 3, 2013 at 10:05 AM, Johannes Berg  wrote:
>
>> The driver or rate control algorithm has to
>> take this into account, I'm not certain that all drivers and
>> algorithms
>> do this correctly (yet).
>
> Just as an example, in rt2x00  we just have to set one bit in the tx
> descriptor to
> force the hw to send out a 1-stream RTS to wake up the peer, from
> rt2x00queue.c:
>
>                 /*
>                  * MIMO PS should be set to 1 for
> STA's using dynamic SM PS
>                  * when using more then one tx stream
> (>MCS7).
>                  */
>                 if (sta && txdesc->u.ht.mcs > 7 &&
>                      sta->smps_mode ==
> IEEE80211_SMPS_DYNAMIC)
>                        
> __set_bit(ENTRY_TXD_HT_MIMO_PS, &txdesc->flags);
>
> HTH,
> Helmut
>
>
> Links:
> ------
> [1] mailto:johannes@sipsolutions.net


      parent reply	other threads:[~2013-04-03  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  7:35 question on SMPS for AP vivekanandah
2013-04-03  8:05 ` Johannes Berg
2013-04-03  8:36   ` vivekanandah
2013-04-03  8:46     ` Johannes Berg
2013-04-04  6:27       ` RFC: SMPS for AP mode vivekanandah
2013-04-09 10:19         ` Johannes Berg
2013-04-09 15:55           ` Naveenraj Subramanian
     [not found]   ` <CAGXE3d_Up9BwfR3gC4uDh_4PNfAaMCME7dVeRnNrpmvc70ZALQ@mail.gmail.com>
2013-04-03  8:37     ` vivekanandah [this message]

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=8a7f0b7f3bc246cc8bacb37f4717b254@posedge.com \
    --to=vivekanandah@posedge.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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