From: Emmanuel Grumbach Date: Thu, 23 Oct 2014 11:42:33 +0000 (+0300) Subject: iwlwifi: mvm: initialize the cur_ucode upon boot X-Git-Tag: v3.18-rc7~15^2^2~2^2~4 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7b358f0652dc09069ee19c4cda52fb20a1fa582a;p=profile%2Fcommon%2Fplatform%2Fkernel%2Flinux-artik7.git iwlwifi: mvm: initialize the cur_ucode upon boot mvm->cur_ucode wasn't set before we actually load the firmware. This caused issues when we boot in RFKILL since we get an RFKILL interrupt upon boot even before we load any firmware. This leads to issues since iwl_mvm_set_hw_rfkill_state (the RFKILL interrupts handler in mvm) relies on this variable. Fix this. Signed-off-by: Emmanuel Grumbach --- diff --git a/drivers/net/wireless/iwlwifi/mvm/ops.c b/drivers/net/wireless/iwlwifi/mvm/ops.c index 48cb25a..27fb0a1 100644 --- a/drivers/net/wireless/iwlwifi/mvm/ops.c +++ b/drivers/net/wireless/iwlwifi/mvm/ops.c @@ -424,6 +424,7 @@ iwl_op_mode_mvm_start(struct iwl_trans *trans, const struct iwl_cfg *cfg, } mvm->sf_state = SF_UNINIT; mvm->low_latency_agg_frame_limit = 6; + mvm->cur_ucode = IWL_UCODE_INIT; mutex_init(&mvm->mutex); mutex_init(&mvm->d0i3_suspend_mutex);