ath10k: fix mismatched wmi api call

Fix to use v10.2 wmi call for firmware v10.2.
It turned out that peer association function was using
v10.1 wmi call for v10.2 firmware during code review.

Signed-off-by: Peter Oh <poh@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>

diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c
index fb63f3374f7166d4c3bca40d9590538ad85e29b3..c2bc8282f6cb169f7d13db32fe62a00aa1d3b10a 100644 (file)
--- a/drivers/net/wireless/ath/ath10k/wmi.c
+++ b/drivers/net/wireless/ath/ath10k/wmi.c
@@ -4194,9 +4194,9 @@ int ath10k_wmi_peer_assoc(struct ath10k *ar,
 
        if (test_bit(ATH10K_FW_FEATURE_WMI_10X, ar->fw_features)) {
                if (test_bit(ATH10K_FW_FEATURE_WMI_10_2, ar->fw_features))
-                       ath10k_wmi_peer_assoc_fill_10_1(ar, skb->data, arg);
-               else
                        ath10k_wmi_peer_assoc_fill_10_2(ar, skb->data, arg);
+               else
+                       ath10k_wmi_peer_assoc_fill_10_1(ar, skb->data, arg);
        } else {
                ath10k_wmi_peer_assoc_fill_main(ar, skb->data, arg);
        }