From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <rmani@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH 1/2] ath6kl: Maintain the listen interval per VIF specific
Date: Thu, 1 Mar 2012 08:28:34 +0200 [thread overview]
Message-ID: <4F4F1712.4070108@qca.qualcomm.com> (raw)
In-Reply-To: <1329745088-23800-1-git-send-email-rmani@qca.qualcomm.com>
On 02/20/2012 03:38 PM, rmani@qca.qualcomm.com wrote:
> From: Raja Mani <rmani@qca.qualcomm.com>
>
> Firmware has the option to support the listen interval
> per vif specific. Fix this.
>
> Listen interval can be set by the TUs or by the number
> of beacons. Current code enables the user to configure
> the listen interval in the unit of 'number of beacons'
> using debugfs entry "listen_interval". Going forward,
> we need to alter the listen interval in the unit of TUs
> to get good power numbers while going to WOW suspend/resume.
>
> Allowing the user to change the listen interval in
> the unit of "number of beacons" in debugfs and changing
> listen interval in wow suspend/resume in the unit of
> time (TUs) would lead us to confuse.
>
> This patch make sures the listen interval is changed only
> in the unit of time (TUs).
>
> Signed-off-by: Raja Mani <rmani@qca.qualcomm.com>
I think these two patches depend on your 'ath6kl: Check wow state before
sending control and data pkt'? At least I got conflicts and they seem to
point to that patch.
If that's the case, I'll put these two patches on hold until the other
patch is applied.
Kalle
next prev parent reply other threads:[~2012-03-01 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 13:38 [PATCH 1/2] ath6kl: Maintain the listen interval per VIF specific rmani
2012-02-20 13:38 ` [PATCH 2/2] ath6kl: Set optimal listen intvl,bmiss,scan params while going to wow suspend rmani
2012-03-01 6:28 ` Kalle Valo [this message]
2012-03-07 7:52 ` [PATCH 1/2] ath6kl: Maintain the listen interval per VIF specific Kalle Valo
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=4F4F1712.4070108@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmani@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).