iwlwifi: pcie: invert values of NO_160 device config entries
authorLuca Coelho <luciano.coelho@intel.com>
Wed, 2 Dec 2020 12:41:50 +0000 (14:41 +0200)
committerKalle Valo <kvalo@codeaurora.org>
Wed, 2 Dec 2020 19:01:33 +0000 (21:01 +0200)
The NO_160 flag specifies if the device doesn't have 160 MHz support,
but we errorneously assumed the opposite.  If the flag was set, we
were considering that 160 MHz was supported, but it's actually the
opposite.  Fix it by inverting the bits, i.e. NO_160 is 0x1 and 160
is 0x0.

Fixes: d6f2134a3831 ("iwlwifi: add mac/rf types and 160MHz to the device tables")
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Link: https://lore.kernel.org/r/iwlwifi.20201202143859.375bec857ccb.I83884286b688965293e9810381808039bd7eedae@changeid
drivers/net/wireless/intel/iwlwifi/iwl-config.h

index ca4967b81d01158ffb4f7fd0dc432c0ada697254..580b07a43856d1c608eb91995c5eb4dd9faf166d 100644 (file)
@@ -491,8 +491,8 @@ struct iwl_cfg {
 #define IWL_CFG_RF_ID_HR               0x7
 #define IWL_CFG_RF_ID_HR1              0x4
 
-#define IWL_CFG_NO_160                 0x0
-#define IWL_CFG_160                    0x1
+#define IWL_CFG_NO_160                 0x1
+#define IWL_CFG_160                    0x0
 
 #define IWL_CFG_CORES_BT               0x0
 #define IWL_CFG_CORES_BT_GNSS          0x5