From: "Pedersen, Thomas" <c_tpeder@qca.qualcomm.com>
To: Kalle Valo <kvalo@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: Wed, 13 Jun 2012 13:50:07 -0700 [thread overview]
Message-ID: <20120613205007.GB3043@pista> (raw)
In-Reply-To: <4FD87FEA.3070208@qca.qualcomm.com>
On Wed, Jun 13, 2012 at 02:56:26PM +0300, Kalle Valo wrote:
> On 06/13/2012 02:37 PM, Luciano Coelho wrote:
> > On Wed, 2012-06-13 at 07:40 +0200, Johannes Berg wrote:
> >> On Tue, 2012-06-12 at 13:43 -0700, Thomas Pedersen wrote:
> >>> Support configuring an RSSI threshold in dBm (s32) when requesting
> >>> scheduled scan, below which a BSS won't be reported by the cfg80211
> >>> driver.
> >>
> >> I'm confused -- were you going to do scheduled scan only? Makes sense,
> >> but if you could maybe change the subject a bit to "specify ... in
> >> scheduled scan"?
> >
> > It makes more sense with scheduled scans, but maybe it is also desirable
> > with normal scans to reduce the amount of scan results traffic?
> >
> > At least if we consider the intermediate scan results that Victor has
> > been working on... We may want to report all scan results at the end,
> > but only send intermediate events if all the matches are satisfied, for
> > example.
> >
> > Just thinking out loud a bit.
>
> Good point.
>
> 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?
If so, maybe it makes sense to convert NL80211_ATTR_SCHED_SCAN_MATCH
into general scan matching parameters instead of having a set for each
scan type?
Thomas
next prev parent reply other threads:[~2012-06-13 20:55 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 [this message]
2012-06-13 21:05 ` Luciano Coelho
2012-06-14 6:29 ` Kalle Valo
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=20120613205007.GB3043@pista \
--to=c_tpeder@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=coelho@ti.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@qca.qualcomm.com \
--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).