From: Jason Huang <Jason.Huang2@infineon.com>
To: <linux-wireless@vger.kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
<brcm80211@lists.linux.dev>, <wlan-kernel-dev-list@infineon.com>
Subject: [PATCH v6 0/5] wifi: brcmfmac: add FT/OKC fast roaming offload support
Date: Fri, 11 Sep 2026 14:56:51 +0800 [thread overview]
Message-ID: <20260911065656.1269623-1-Jason.Huang2@infineon.com> (raw)
In-Reply-To: <20260821-upstream-wireless-next-main-jason-11r-support-v1-v5-0-eeab4fda0f31@infineon.com>
From: Jason Huang <jason.huang2@infineon.com>
Hi,
This series adds nl80211 and brcmfmac support for firmware fast roaming
offload covering FT and OKC.
Some Broadcom/Infineon firmware can offload FT or OKC roaming without
advertising full 802.1X 4-way handshake offload. The series adds a new
nl80211 extended feature bit for this capability, lets userspace install
and delete PMK material when the driver advertises it, and wires the
capability through brcmfmac based on firmware FBT/OKC support.
For brcmfmac, the series tracks FBT and OKC firmware capabilities, keeps
the firmware supplicant profile state distinct for roaming offload, passes
PMK material to firmware for FT/OKC, and reports port authorization after
successful offloaded roaming.
Changes in v6:
- Rename the nl80211 extended feature to
NL80211_EXT_FEATURE_FAST_ROAM_OFFLOAD to better describe that userspace
offloads fast-roaming handling to the driver/firmware. The feature covers
both FT and OKC.
- Reorder the nl80211 PMK capability checks to avoid the line-length
warning.
- Allow nl80211_del_pmk() for FAST_ROAM_OFFLOAD-only drivers, matching
nl80211_set_pmk(), so userspace can delete PMK material it was allowed to
install.
Carella Chen (3):
wifi: nl80211: add fast roam offload extended feature
wifi: brcmfmac: detect firmware FBT and OKC support
wifi: brcmfmac: advertise firmware fast roam offload support
Darren Li (2):
wifi: brcmfmac: add PMK programming for firmware roaming offload
wifi: brcmfmac: report port authorization after offloaded roaming
.../broadcom/brcm80211/brcmfmac/cfg80211.c | 125 ++++++++++++++++--
.../broadcom/brcm80211/brcmfmac/cfg80211.h | 5 +-
.../broadcom/brcm80211/brcmfmac/feature.c | 2 +
.../broadcom/brcm80211/brcmfmac/feature.h | 4 +-
include/uapi/linux/nl80211.h | 5 +
net/wireless/nl80211.c | 10 +-
6 files changed, 136 insertions(+), 15 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2026-09-11 6:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 7:56 [PATCH v5 0/5] brcmfmac: add FT/OKC roaming offload support Jason Huang
2026-08-21 7:56 ` [PATCH v5 1/5] wifi: nl80211: add roam offload extended feature Jason Huang
2026-08-22 18:36 ` Arend van Spriel
2026-08-30 9:14 ` Arend van Spriel
2026-09-01 7:14 ` HungTsung Huang
2026-09-01 8:56 ` Arend van Spriel
2026-09-04 8:38 ` Johannes Berg
2026-09-08 5:59 ` HungTsung Huang
2026-08-21 7:56 ` [PATCH v5 2/5] wifi: brcmfmac: detect firmware FBT and OKC support Jason Huang
2026-08-21 7:56 ` [PATCH v5 3/5] wifi: brcmfmac: add PMK programming for firmware roaming offload Jason Huang
2026-08-21 7:56 ` [PATCH v5 4/5] wifi: brcmfmac: report port authorization after offloaded roaming Jason Huang
2026-08-22 18:24 ` [PATCH v5 0/5] brcmfmac: add FT/OKC roaming offload support Arend van Spriel
2026-08-22 18:26 ` Arend van Spriel
2026-08-24 3:08 ` HungTsung Huang
2026-08-24 2:27 ` [PATCH v5 5/5] wifi: brcmfmac: advertise firmware roam " Jason Huang
2026-09-11 6:56 ` Jason Huang [this message]
2026-09-11 6:56 ` [PATCH v6 1/5] wifi: nl80211: add fast roam offload extended feature Jason Huang
2026-09-11 6:56 ` [PATCH v6 2/5] wifi: brcmfmac: detect firmware FBT and OKC support Jason Huang
2026-09-11 6:56 ` [PATCH v6 3/5] wifi: brcmfmac: add PMK programming for firmware roaming offload Jason Huang
2026-09-11 6:56 ` [PATCH v6 4/5] wifi: brcmfmac: report port authorization after offloaded roaming Jason Huang
2026-09-11 6:56 ` [PATCH v6 5/5] wifi: brcmfmac: advertise firmware fast roam offload support Jason Huang
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=20260911065656.1269623-1-Jason.Huang2@infineon.com \
--to=jason.huang2@infineon.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wlan-kernel-dev-list@infineon.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