From: Vivekananda Holla <vivekanandah@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Patch] mac80211: add rts-cts for dynamic SMPS stations
Date: Mon, 15 Apr 2013 16:13:35 +0530 [thread overview]
Message-ID: <516BD9D7.3060804@posedge.com> (raw)
In-Reply-To: <1366017844.8361.7.camel@jlt4.sipsolutions.net>
Hi Johannes,
I ran checkpatch.pl script and found some trailing white spaces in the patch which i have now
corrected.
Also,i had initially placed my code in minstrel_ht_get_rate but saw that the minstrel code is being
changed.
hence, moved the code in to ieee80211_tx_h_rate_ctrl function.
there is a check in this function
if (info->control.rates[i].flags & IEEE80211_TX_RC_MCS) {
WARN_ON(info->control.rates[i].idx > 76);
continue;
}
I feel it would be okay to move the code for dyn_smps within this loop as
this would solve the check for MCS rates.
however i am not sure whether all ht rates flag settings need to be handled within minstrel_ht?
if (info->control.rates[i].flags & IEEE80211_TX_RC_MCS) {
WARN_ON(info->control.rates[i].idx > 76);
+ if (dyn_smps) {
+ if ((info->control.rates[i].idx > 7) &&
+ (info->control.rates[i].idx != 32))
+ info->control.rates[i].flags |=
+ IEEE80211_TX_RC_USE_RTS_CTS;
continue;
}
awaiting your inputs
thanks and regards
Vivek
On 04/15/2013 02:54 PM, Johannes Berg wrote:
> Vivek,
>
> Please work with some of your colleagues at posedge to submit a proper
> patch. This is formatted completely wrongly in many ways.
>
>> + if (dyn_smps) {
>> + if ((info->control.rates[i].idx > 7) &&
>> + (info->control.rates[i].idx != 32))
> This is also completely wrong. (hint, there are non-HT bitrates still)
>
> johannes
>
prev parent reply other threads:[~2013-04-15 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 6:33 [Patch] mac80211: add rts-cts for dynamic SMPS stations Vivekananda Holla
2013-04-15 9:24 ` Johannes Berg
2013-04-15 10:43 ` Vivekananda Holla [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=516BD9D7.3060804@posedge.com \
--to=vivekanandah@posedge.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;
as well as URLs for NNTP newsgroup(s).