On Tue, Jun 2, 2015 at 2:06 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2015-06-01 at 22:44 +0530, Chaitanya T K wrote: >> From: Chaitanya T K <chaitanya.mgit@xxxxxxxxx> >> >> If suspended during TX in progress, there can be >> race where the driver is put of of power-save due >> to TX and during suspend dynamic_ps_time is cancelled >> and TX packet is flushed, leaving the driver in ACTIVE >> even after resuming until dynamic_ps_time puts >> driver back in DOZE. (Which only happens if there >> is another TX). >> >> This can lead high power consumption of chipset during (or) >> after resuming also. > > This isn't what your patch is actually doing though. You need to mention > WoWLAN at the very least in your commit log; Yes, WoWLAN is enabled in our testing. Without wowlan the connection will not be intact. So i assumed the check "is_associated" would imply wowlan. > or are you just randomly > changing the code until it fixes your bug? :) I am not that lucky to find a proper fix that way :-). -- 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
