Linux wireless drivers development
 help / color / mirror / Atom feed
From: <vivekanandah@posedge.com>
To: <linux-wireless@vger.kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>, <nbd@openwrt.org>
Subject: RFC: SMPS for AP mode
Date: Thu, 4 Apr 2013 11:57:07 +0530	[thread overview]
Message-ID: <021a065e3ab402466e8049b2f4cd3fdd@posedge.com> (raw)
In-Reply-To: <1364978764.8351.6.camel@jlt4.sipsolutions.net>

hi,

based on the discussion, i have come out with an RFC for SMPS support 
for AP in minstrel_ht. kindly see the explanation below and indicate to 
me, if this okay or any changes are required?

RFC To send out RTS for AP connected to a dynamic SMPS station

This code change addresses the AP requirement of sending out a
RTS frame when dynamic SMPS is enabled at the station

the minstrel_ht rate module needs to provide the lower driver layer
an indication of enabling RTS frame transmission for an AP connected
to a dynamic SMPS station.

the SMPS state of the station is stored in the ieee80211_sta 
structure's ht_cap variable.

the minstrel_ht_get_rate function can be modified to check if the 
station is a dynamic SMPS
station and a new flag can be incorporated for the ieee80211_tx_info 
flags (e.g. IEEE80211_TX_CTL_SMPS_SET_RTS)
that indicates to the lower layer that the station is a dynamic SMPS 
enabled station.

the lower AP driver can then enable RTS before the first frame 
transmission to the station by checking for the above flag.

thanks and regards
Vivek




On Wed, 03 Apr 2013 10:46:04 +0200, Johannes Berg wrote:
>> i see that the rate_control_rate_update is called with the
>> IEEE80211_RC_SMPS_CHANGED flag. however, i see that the minstrel_ht 
>> code
>> does not check for SMPS with respect to RTS.
>
> It's very well possible that minstrel doesn't implement this 
> correctly.
> I don't care all that much right now about minstrel, so it's up to 
> those
> who do :)
>
>> Also, the code - rate_control_rate_update calls - sta_rc_update
>> mac80211 op. i was first thinking that i could use this for the AP 
>> side
>> notification to driver layer. however, a comment for sta_rc_update
>> indicates that it is to be used only when 
>> IEEE80211_HW_HAS_RATE_CONTROL
>> is true.
>> this led to the confusion.
>>
>> Can this op be used to update the driver about change in station's 
>> SMPS
>> mode for AP ?
>
> Well, in theory it could be, but it doesn't make sense. If you have a
> rate control algorithm in software (like minstrel) then that should
> likely configure the RTS, and rate control is updated via the rate
> control rate_update() callback instead of via the driver.
>
> johannes

  reply	other threads:[~2013-04-04  6:27 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       ` vivekanandah [this message]
2013-04-09 10:19         ` RFC: SMPS for AP mode Johannes Berg
2013-04-09 15:55           ` Naveenraj Subramanian
     [not found]   ` <CAGXE3d_Up9BwfR3gC4uDh_4PNfAaMCME7dVeRnNrpmvc70ZALQ@mail.gmail.com>
2013-04-03  8:37     ` question on SMPS for AP vivekanandah

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=021a065e3ab402466e8049b2f4cd3fdd@posedge.com \
    --to=vivekanandah@posedge.com \
    --cc=johannes@sipsolutions.net \
    --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