Add a vendor specific roam status of background scan abort

When user space triggers a scan, the firmware aborts background scan,
and uses the roam status QCA_ROAM_FAIL_REASON_CURR_AP_STILL_OK instead
of "Invalid roam failures reason".

Signed-off-by: Chunquan Luo <quic_chunquan@quicinc.com>
This commit is contained in:
Chunquan Luo 2023-04-19 04:28:06 -07:00 committed by Jouni Malinen
parent b171c5e4d5
commit c858a6360b

View file

@ -4966,6 +4966,8 @@ enum qca_vendor_roam_triggers {
* @QCA_ROAM_FAIL_REASON_SAE_PREAUTH_TIMEOUT: WPA3-SAE pre-authentication times
* out.
* @QCA_ROAM_FAIL_REASON_SAE_PREAUTH_FAIL: WPA3-SAE pre-authentication fails.
* @QCA_ROAM_FAIL_REASON_CURR_AP_STILL_OK: Roam scan did not happen since the
* current network conditions are fine.
*/
enum qca_vendor_roam_fail_reasons {
QCA_ROAM_FAIL_REASON_NONE = 0,
@ -4998,6 +5000,7 @@ enum qca_vendor_roam_fail_reasons {
QCA_ROAM_FAIL_REASON_SAE_INVALID_PMKID = 27,
QCA_ROAM_FAIL_REASON_SAE_PREAUTH_TIMEOUT = 28,
QCA_ROAM_FAIL_REASON_SAE_PREAUTH_FAIL = 29,
QCA_ROAM_FAIL_REASON_CURR_AP_STILL_OK = 30,
};
/*