From: <vivekanandah@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Patch] mac80211: SMPS for AP Mode
Date: Wed, 10 Apr 2013 22:21:44 -0700 [thread overview]
Message-ID: <403b23c5df64cb4e0d6ffbabb7ca804f@posedge.com> (raw)
In-Reply-To: <1365592730.8388.8.camel@jlt4.sipsolutions.net>
Hi johannes,
my first patch was based on the premise that an AP cannot switch its
receive chains off as it would be servicing multiple clients.
i was not aware if an AP can set SMPS at its end, hence i wanted to
make sure that control be provided to the lower layer driver to take a
call on the same.
in my hurry to submit my first patch, i did overlook the MCS rate
dependency and accept my mistake.
i have outlined three requirements based on my understanding for SMPS
code and have also incorporated a code snippet. if you are okay with the
code snippet, i will provide a patch for the same.
1) check if the receiving station has Dynamic SMPS on
2) check if the current MCS rate is greater than a single stream rate
for the first rate
3) if conditions 1 and 2 are true, set the RTS_CTS flag for the first
rate that will
be attempted to be transmitted
if ((sta->smps_mode == IEEE80211_SMPS_DYNAMIC) && (ar[0].idx > 7))
ar[0].flags |= IEEE80211_TX_RC_USE_RTS_CTS;
i respect the time you have spent on looking into my code and apologize
for the inconvenience caused. this is my first patch submission and i
have made some mistakes :)
thanks and regards
Vivek
On Wed, 10 Apr 2013 13:18:50 +0200, Johannes Berg wrote:
> On Wed, 2013-04-10 at 16:12 +0530, Vivekananda Holla wrote:
>> patch for SMPS mode. after discussion, setting the
>> IEEE80211_TX_RC_USE_RTS_CTS flag for first rate if dynamic SMPS is on
>> in the receiving station
>
> Please line-break your description and remove all the
> discussion-related
> stuff etc. from the commit log -- see
>
> http://wireless.kernel.org/en/developers/Documentation/SubmittingPatches
>
> Also, it should set the flag depending on the MCS ... Please try to
> understand what you're actually doing and trying to do before
> submitting
> random patches. It's not an effective use of my time to be reviewing
> patches if you don't know what you're doing.
>
> johannes
next prev parent reply other threads:[~2013-04-11 5:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 10:42 [Patch] mac80211: SMPS for AP Mode Vivekananda Holla
2013-04-10 11:18 ` Johannes Berg
2013-04-11 5:21 ` vivekanandah [this message]
2013-04-11 8:22 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2013-04-10 8:54 Vivekananda Holla
2013-04-10 8:55 ` Johannes Berg
2013-04-10 9:35 ` Vivekananda Holla
2013-04-10 9:46 ` Johannes Berg
2013-04-10 9:47 ` Johannes Berg
2013-04-10 9:55 ` Vivekananda Holla
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=403b23c5df64cb4e0d6ffbabb7ca804f@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 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.