From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Pedersen, Thomas" <c_tpeder@qca.qualcomm.com>
Cc: Luciano Coelho <coelho@ti.com>,
Johannes Berg <johannes@sipsolutions.net>,
<ath6kl-devel@qualcomm.com>, <linux-wireless@vger.kernel.org>,
<victorg@ti.com>
Subject: Re: [PATCH] nl80211: specify RSSI threshold when scanning
Date: Thu, 14 Jun 2012 09:29:21 +0300 [thread overview]
Message-ID: <4FD984C1.8090903@qca.qualcomm.com> (raw)
In-Reply-To: <20120613205007.GB3043@pista>
On 06/13/2012 11:50 PM, Pedersen, Thomas wrote:
> On Wed, Jun 13, 2012 at 02:56:26PM +0300, Kalle Valo wrote:
>
>> Funnily enough I don't have any idea how ath6kl has implemented this
>> feature, but in theory this feature is useful also for the current
>> normal scan (when the firmware/hardware supports it) as we can avoid
>> host wakeups. If there are 10 APs, but all are below the RSSI threshold,
>> we will have only 1 host wakeup (scan ready event) opposed to 11 wakeups
>> (10 AP found events plus 1 scan ready event).
>
> But can the host even sleep on normal scans?
It's "implementation defined", the good ones can and bad ones can't :)
But from our (wireless developer) perspective we don't need to care
about that, our job is to minimise all possible host wakeup events
(timers, interrupts etc) as much as possible. That will allow the host
to sleep more.
Kalle
next prev parent reply other threads:[~2012-06-14 6:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 20:43 [PATCH] nl80211: specify RSSI threshold when scanning Thomas Pedersen
2012-06-13 5:40 ` Johannes Berg
2012-06-13 5:53 ` Holger Schurig
2012-06-13 5:54 ` Johannes Berg
2012-06-13 20:45 ` Pedersen, Thomas
2012-06-14 6:48 ` Johannes Berg
2012-06-13 11:37 ` Luciano Coelho
2012-06-13 11:56 ` Kalle Valo
2012-06-13 20:50 ` Pedersen, Thomas
2012-06-13 21:05 ` Luciano Coelho
2012-06-14 6:29 ` Kalle Valo [this message]
2012-06-14 19:39 ` Chadd, Adrian
2012-06-14 20:21 ` Singh, Naveen
2012-06-14 20:41 ` Chadd, Adrian
2012-06-14 21:18 ` Singh, Naveen
2012-06-14 22:16 ` Chadd, Adrian
2012-06-15 4:40 ` Luciano Coelho
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=4FD984C1.8090903@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=c_tpeder@qca.qualcomm.com \
--cc=coelho@ti.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=victorg@ti.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).