From: James Cameron <quozl@laptop.org>
To: Bing Zhao <bzhao@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] mwifiex: block work queue while suspended
Date: Wed, 28 May 2014 12:01:28 +1000 [thread overview]
Message-ID: <20140528020128.GG4151@us.netrek.org> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430F70F5E39F@SC-VEXCH1.marvell.com>
On Tue, May 27, 2014 at 04:39:07PM -0700, Bing Zhao wrote:
> Hi James,
>
> > > To understand what is happening here could you apply attached debug
> > > patch to generate logs, or enable dynamic_debug for that?
> >
> > Here's a dynamic_debug log.
> >
> > Note the point of failure is the "mmc0: Timeout waiting for hardware
> > interrupt." message, which occurs in the driver SDIO interrupt
> > function, which began execution in a critical time period after driver
> > suspend but before platform suspend.
> >
> > We use a GPIO to wake from WLAN.
>
> This doesn't match the gpio parameter configured in hscfg command
> 0xe5.
You're right, and I'm quite wrong. Sorry about that. I misread our
code.
Correction, we use SDIO to wake from WLAN.
We set gap to 0xff, which we think is a special value that means the
device will wait for the host to acknowledge before sending data to
the host.
Looking through history of development, we thought that this would
avoid a race condition, where the host starts to suspend, configures
the device for host sleep, but the device may wake in the time before
the host suspends.
We don't see this "mmc0: Timeout waiting for hardware interrupt."
problem unless we use WPA2. It does not reproduce on an open access
point.
--
James Cameron
http://quozl.linux.org.au/
next prev parent reply other threads:[~2014-05-28 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 1:24 [RFC] mwifiex: block work queue while suspended James Cameron
2014-05-22 3:50 ` Bing Zhao
2014-05-22 5:46 ` James Cameron
2014-05-23 4:12 ` Bing Zhao
2014-05-26 8:01 ` James Cameron
2014-05-27 23:39 ` Bing Zhao
2014-05-28 2:01 ` James Cameron [this message]
2014-05-28 4:35 ` Bing Zhao
2014-05-28 4:49 ` James Cameron
2014-05-28 5:04 ` Bing Zhao
2014-05-29 1:22 ` James Cameron
2014-05-29 2:10 ` Bing Zhao
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=20140528020128.GG4151@us.netrek.org \
--to=quozl@laptop.org \
--cc=bzhao@marvell.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).