From: Arend van Spriel <arend@broadcom.com>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] iwlwifi: mvm: abort scheduled scan upon RFKILL
Date: Sun, 18 Jan 2015 23:14:09 +0100 [thread overview]
Message-ID: <54BC3031.7060308@broadcom.com> (raw)
In-Reply-To: <1421612283-27012-1-git-send-email-emmanuel.grumbach@intel.com>
On 01/18/15 21:18, Emmanuel Grumbach wrote:
> When we have an active scheduled scan, and the RFKILL
> interrupt kicks in, the stack will cancel the scheduled
> scan as part of the down flow. But cancelling scheduled
> scan usually implies sending a command to the firwmare
> which has been killed as part of the RFKILL interrupt
> handling.
> Because of that, we returned an error to mac80211 when
> it asked to stop the scheduled scan and didn't notify the
> end of the scheduled scan. Besides a fat warning, this led
> to a situation in which cfg80211 would refuse any new scan
> request.
>
> To disentangle this, fake that the scheduled scan has been
> stopped without sending the command to the firwmare, return
> 0 after having properly let cfg80211 know that the scan
> has been cancelled.
>
> This is basically the same as:
> commit 9b520d84957d63348e87c0f2cbd21d86e1e8f2f2
> Author: Emmanuel Grumbach<emmanuel.grumbach@intel.com>
> Date: Tue Nov 4 15:54:11 2014 +0200
>
> iwlwifi: mvm: abort scan upon RFKILL
>
> This code existed but not for all the different FW APIs
> we support.
> Fix this.
>
> but for the scheduled scan case.
So looking at the patch I guess cfg80211 will still issues a WARN_ON, right?
Regards,
Arend
> Link: http://permalink.gmane.org/gmane.linux.kernel.wireless.general/133232
> Reported-by: Linus Torvalds<torvalds@linux-foundation.org>
> Signed-off-by: Emmanuel Grumbach<emmanuel.grumbach@intel.com>
> ---
> drivers/net/wireless/iwlwifi/mvm/scan.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/net/wireless/iwlwifi/mvm/scan.c b/drivers/net/wireless/iwlwifi/mvm/scan.c
> index 3fbba4b..844bf7c 100644
> --- a/drivers/net/wireless/iwlwifi/mvm/scan.c
> +++ b/drivers/net/wireless/iwlwifi/mvm/scan.c
> @@ -1107,6 +1107,12 @@ int iwl_mvm_scan_offload_stop(struct iwl_mvm *mvm, bool notify)
> return iwl_umac_scan_stop(mvm, IWL_UMAC_SCAN_UID_SCHED_SCAN,
> notify);
>
> + if (mvm->scan_status == IWL_MVM_SCAN_NONE)
> + return 0;
> +
> + if (iwl_mvm_is_radio_killed(mvm))
> + goto out;
> +
> if (mvm->scan_status != IWL_MVM_SCAN_SCHED&&
> (!(mvm->fw->ucode_capa.api[0]& IWL_UCODE_TLV_API_LMAC_SCAN) ||
> mvm->scan_status != IWL_MVM_SCAN_OS)) {
> @@ -1143,6 +1149,7 @@ int iwl_mvm_scan_offload_stop(struct iwl_mvm *mvm, bool notify)
> if (mvm->scan_status == IWL_MVM_SCAN_OS)
> iwl_mvm_unref(mvm, IWL_MVM_REF_SCAN);
>
> +out:
> mvm->scan_status = IWL_MVM_SCAN_NONE;
>
> if (notify) {
next prev parent reply other threads:[~2015-01-18 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 20:16 pull request: iwlwifi 2015-01-15 Grumbach, Emmanuel
2015-01-18 20:18 ` [PATCH] iwlwifi: mvm: abort scheduled scan upon RFKILL Emmanuel Grumbach
2015-01-18 22:14 ` Arend van Spriel [this message]
2015-01-19 5:57 ` Grumbach, Emmanuel
2015-01-19 7:53 ` pull request: iwlwifi 2015-01-15 Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BC3031.7060308@broadcom.com \
--to=arend@broadcom.com \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).