On 10/31/2011 11:55 AM, Raja Mani wrote: > On Friday 28 October 2011 06:48 PM, Kalle Valo wrote: >> On 10/25/2011 01:37 PM, rmani@xxxxxxxxxxxxxxxx wrote: >>> --- a/drivers/net/wireless/ath/ath6kl/txrx.c >>> +++ b/drivers/net/wireless/ath/ath6kl/txrx.c >>> @@ -1081,6 +1081,8 @@ void ath6kl_rx(struct htc_target *target, struct htc_packet *packet) >>> return; >>> } >>> >>> + ath6kl_pm_check_wow_status(ar); >> >> Now we resume from two places, cfg80211 resume handler and here. Why do >> we need to do that? Why isn't cfg80211 resume handler enough? > > This path hits when the target wants to wake up the host. When given WOW > pattern matches, the target will pull SDIO data line to wake up the > host. During that time , the control will reach here (sdio irq handler > -> ath6kl_rx function), not to cfg80211 resume. I don't understand this. Are you saying that host resumes but cfg80211 resume handler is not called? It doesn't make sense, every suspend call should have an equivalent resume call. If that doesn't happen, something is broken somewhere. Kalle -- 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
