From: Kalle Valo <kvalo@qca.qualcomm.com>
To: shonmou li <shonmou@gmail.com>
Cc: <ath6kl-devel@qualcomm.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Raja Mani <rmani@qca.qualcomm.com>
Subject: Re: [PATCH] ath6kl: avoiding 80211 scan does not complete before start scheduled scan.
Date: Wed, 21 Mar 2012 10:09:35 +0200 [thread overview]
Message-ID: <4F698CBF.5080702@qca.qualcomm.com> (raw)
In-Reply-To: <CADhJdvDpdQzJHQ-hLnASyyCKc2rzG_aBMtTm0rND7d1xdkudyg@mail.gmail.com>
Hi Shonmou,
please include linux-wireless in CC.
On 03/20/2012 02:15 PM, shonmou li wrote:
> Hi Kalle,
>
> Thanks for your reply. I have added descriptions and signed-off-line in
> the patch file.
>
> When i port the ar6003 driver into android device (ICS), I used the
> following procedure to trigger this bug every time:
>
> 1. enable wifi in android setting menu.
> 2. connect with an AP.
> 3. After device enter suspending state, power off the connected AP.
> 4. At this moment, the device would resume to deal with disconnection event.
> 5. After device suspend again, press power on button to wake the device on.
> 6. Go to setting menu wifi page, press scan button.
> 7. You will get "Scan trigger failed: ret=-16 (Device or resource
> busy)" on android main log.
>
> The log file is in attached file log1.txt.
>
> If FW has the capability to check the status of normal scan and sscan, i
> think it is better. But it should add external information or API in
> order to notify user space what scan mode it is.
Thanks, I understand the issue better. I think your patch is a good fix
for now. If there are more problems still we can fix those separately.
Raja also saw the same problem and he confirmed that your patch fixes
the issue.
I have applied the patch to ath6kl.git with minor modifications to the
commit log. Thank you very much for the patch.
Kalle
commit b4d13d3b70b085ef9b8e0bf7132d502d77d9ffc6
Author: Kalle Valo <kvalo@qca.qualcomm.com>
Date: Wed Mar 21 10:01:09 2012 +0200
ath6kl: abort normal scan when scheduled scan is started
If the device disconnects from an AP when it is in suspending state.
You will
get the following message from wpa_supplicant after waking the
device up and
sending scan request:
"Scan trigger failed: ret=-16 (Device or resource busy)"
Fix the issue by sending a scan complete event before starting scheduled
scan.
kvalo: cosmetic changes to commit log
Signed-off-by: Isaac.li <shonmou@gmail.com>
Tested-by: Raja Mani <rmani@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
next prev parent reply other threads:[~2012-03-21 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADhJdvDbAORKoWUxLdcz7Jq2dt9DKEPzBwgmiNvZsj6iU2K9Kw@mail.gmail.com>
2012-03-20 8:04 ` [PATCH] ath6kl: avoiding 80211 scan does not complete before start scheduled scan Kalle Valo
2012-03-20 8:07 ` Kalle Valo
[not found] ` <CADhJdvDpdQzJHQ-hLnASyyCKc2rzG_aBMtTm0rND7d1xdkudyg@mail.gmail.com>
2012-03-21 8:09 ` Kalle Valo [this message]
2012-03-21 6:09 ` Raja Mani
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=4F698CBF.5080702@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmani@qca.qualcomm.com \
--cc=shonmou@gmail.com \
/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).