All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: "Vamsi, Krishna" <vamsin@qti.qualcomm.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"Malinen, Jouni" <jouni@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] cfg80211: Add support to sched scan to report better BSSs
Date: Wed, 7 Dec 2016 21:03:23 +0100	[thread overview]
Message-ID: <280cb669-2360-d4fc-779b-80196c944e2e@broadcom.com> (raw)
In-Reply-To: <dc960243db2b452f97721dad49f0a63b@aphydexm01b.ap.qualcomm.com>

On 7-12-2016 10:33, Vamsi, Krishna wrote:
>> -----Original Message-----
>> From: Johannes Berg [mailto:johannes@sipsolutions.net]
> 
>> What about Arend's comment regarding this functionality overlapping with the
>> BSS selection offload configuration?
>>
>> Do you think there's any ability to share attributes/functionality?
> 
> Hi Johannes,
> 
> I think the later comment from Luca on this which I pasted below is more agreeable.
> 
> Yes, similar but not quite the same.  The existing case is for finding BSSs that are worth waking the host up for (while disconnected), so it needs to be better than the RSSI passed (absolute number).  Now this is about relative RSSI as compared to the current connection, so RELATIVE_RSSI is different than RSSI and I think the same attribute should not be used, to avoid confusion.

I noticed the response from Luca, but did not get back on this. I know
it is not the same, but what I meant is whether we could extend it so it
also covers your scenario.

Regards,
Arend

  reply	other threads:[~2016-12-07 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 21:59 [PATCH v2 1/2] nl80211: Use different attrs for BSSID and random MAC addr in scan req Jouni Malinen
2016-12-02 21:59 ` [PATCH v2 2/2] cfg80211: Add support to sched scan to report better BSSs Jouni Malinen
2016-12-07  9:25   ` Johannes Berg
2016-12-07  9:33     ` Vamsi, Krishna
2016-12-07 20:03       ` Arend Van Spriel [this message]
2016-12-08 17:52         ` Malinen, Jouni
2016-12-08 20:35           ` Arend Van Spriel
2016-12-13 15:56             ` Johannes Berg
2016-12-15 11:06               ` Malinen, Jouni
2016-12-16  9:56                 ` Johannes Berg
2016-12-20 20:52                   ` Malinen, Jouni
2016-12-21  9:18                     ` Arend Van Spriel
2017-01-04 13:32                       ` Johannes Berg
2017-01-04 13:34                     ` Johannes Berg
2016-12-07 20:11   ` Arend Van Spriel

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=280cb669-2360-d4fc-779b-80196c944e2e@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vamsin@qti.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 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.