From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>, Jouni Malinen <j@w1.fi>
Subject: Re: [RFC V2 0/3] nl80211: allow configuration of BSS selection
Date: Thu, 14 Jan 2016 10:15:07 +0100 [thread overview]
Message-ID: <5697671B.2040302@broadcom.com> (raw)
In-Reply-To: <1452678583-20086-1-git-send-email-arend@broadcom.com>
On 01/13/2016 10:49 AM, Arend van Spriel wrote:
> This patch series adds support for configuration of BSS selection done by
> the driver and/or firmware. It allows user-space to pass selection criteria
> with the NL80211_CMD_CONNECT using NL80211_ATTR_BSS_SELECT. When user-space
> does provide this attribute and no explicit BSSID is provided it will pass
> the BSS selection criteria to the driver if the driver supports it.
>
> When multiple BSS-es are found belonging to the same ESS, ie. Infra-BSS with
> same SSID, the criteria can be used to select a BSS. The criteria defined are:
>
> 1. RSSI based selection.
> 2. Band selection, RSSI based selection.
> 3. RSSI adjustment in given band, RSSI based selection.
>
> V2:
> - incorporate comments from Johannes Berg (may have missed some).
> - split nl80211 patch in two separate patches.
I looked into the suggested mac80211 "demo", but it seems this bss
selection could be handled in net/wireless/sme.c for drivers support
.assoc() and friends instead of .connect(). However, I recall Jouni
suggesting to have NL80211_ATTR_BSS_SELECT in NL80211_CMD_ASSOC as well.
So I guess wpa_s uses that command directly?
Regards,
Arend
> Arend van Spriel (3):
> nl80211: add extended feature for BSS selection support
> nl80211: add bss selection attribute to CONNECT command
> brcmfmac: add support for nl80211 BSS_SELECT feature
>
> drivers/net/wireless/brcm80211/brcmfmac/cfg80211.c | 63 ++++++++++++++++
> drivers/net/wireless/brcm80211/brcmfmac/common.c | 38 ++++++----
> drivers/net/wireless/brcm80211/brcmfmac/core.h | 1 +
> include/net/cfg80211.h | 34 +++++++++
> include/uapi/linux/nl80211.h | 52 +++++++++++++
> net/wireless/core.c | 5 ++
> net/wireless/nl80211.c | 86 ++++++++++++++++++++++
> 7 files changed, 264 insertions(+), 15 deletions(-)
>
next prev parent reply other threads:[~2016-01-14 9:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 9:49 [RFC V2 0/3] nl80211: allow configuration of BSS selection Arend van Spriel
2016-01-13 9:49 ` [RFC V2 1/3] nl80211: add extended feature for BSS selection support Arend van Spriel
2016-01-14 11:00 ` Johannes Berg
2016-01-13 9:49 ` [RFC V2 2/3] nl80211: add bss selection attribute to CONNECT command Arend van Spriel
2016-01-14 11:10 ` Johannes Berg
2016-01-14 11:12 ` Johannes Berg
2016-01-18 9:34 ` Arend van Spriel
2016-01-19 13:20 ` Johannes Berg
2016-01-19 22:33 ` Arend van Spriel
2016-01-20 9:30 ` Johannes Berg
2016-01-20 14:02 ` Johannes Berg
2016-01-20 21:53 ` Arend van Spriel
2016-01-21 6:57 ` Peer, Ilan
2016-01-13 9:49 ` [RFC V2 3/3] brcmfmac: add support for nl80211 BSS_SELECT feature Arend van Spriel
2016-01-14 9:15 ` Arend van Spriel [this message]
2016-01-14 9:20 ` [RFC V2 0/3] nl80211: allow configuration of BSS selection Johannes Berg
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=5697671B.2040302@broadcom.com \
--to=arend@broadcom.com \
--cc=j@w1.fi \
--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 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).