Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: vivekanandah@posedge.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: question on SMPS for AP
Date: Wed, 03 Apr 2013 10:46:04 +0200	[thread overview]
Message-ID: <1364978764.8351.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <7a1a483e9382db42e8f648c3933bc2cd@posedge.com>


> 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-03  8:46 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 [this message]
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     ` 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=1364978764.8351.6.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vivekanandah@posedge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox