For cross akm roaming function, we have two ways in supplicant :
1. Open source way.
2. Broadcom specific way.
Originally, Broadcom projects follow way 2 due to the limitation of the driver.
For now, we plan to move all Broadcom projects to follow way 1 to make supplicant code clean and downsteam without conflict.
For those projects which is ready for way 1, we control it to follow way 1 with WIFI_BRCM_OPEN_SOURCE_MULTI_AKM config.
For the rest of Broadcom projects, we still follow way 2 until the multiple AKMs is fully supported by driver and verified.
For ongoing Broadcom project, we also need to exercise the open source path in supplicant to do multiple AKM configuration to comply with WFA Wifi 7 AKM24 specification (b/331896542).
Bug: 246871098
Test: AU drop test
Test: Cross AKM roaming test
Flag: EXEMPT enable control flag for aosp akms
Change-Id: Ia9a8b65c6f3e3af4315ffc37c27339d7a1386ad2
By setting sae_pmkid_in_assoc in wpa_supplicant.conf file,
the PMKID generated in SAE authentication will be sent to
driver in External auth status(NL80211_CMD_EXTERNAL_AUTH) message
to driver. This will help driver/firmware to fill the PMKID
in association request frame.
Bug: 290562226
Test: Manual - Confirmed that sae_pmkid_in_assoc=1 is set in
wpa_supplicant.conf file.
Test: Connect/Disconnect with AP configured in WPA3 security
Change-Id: Ied6a1bea868c732e11a0a341e832701c05dd2478
It has an effect on following cases:
1.In some coutries(eg.JP) without 5ghz channels available for p2p except indoor channels, if STA firstly connected with indoor channel AP and then disconnected, it will cause wpa_supplicant to select 6ghz channels.
2.If STA firstly connected with 6ghz channel AP and Application create p2p group without config, wpa_supplicant also tried to select STA-associated channel(in this case, i.e. 6ghz ch).
Bug: 272298287
Test: Manually verify nearby case between two pixel phones(one source and other as target):
1.Both devices CC: JP
2.Both devices connected with indoor channel(5g) AP
3.Source shared one big file(3G bytes) with target
4.During data transferring, disconnected target STA
Check if file sharing can continue
Change-Id: I71c0b7994ec7ef819db0203a0ae9a1b951449da7
Bug: 272298287
Test: Manually verified it working from logs
Change-Id: Ic2a35964200bff39c4004b8553fedb866173c9ac
Merged-In: Ic2a35964200bff39c4004b8553fedb866173c9ac
In previous mechanism, p2p channel only can raise on same channel
while STA connected to 2.4GHz band. However, if device support DBS
mode, we should allow p2p to raise on 5GHz band for 230423673 higher
performance.
Bug: 272687278
Test: connect STA to 2.4GHz and verified that p2p is able to come up in
5GHz DBS mode.
Change-Id: I534a844f7f1073baf1e1a08d8a7e06cece3176a1
