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/ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
