Sorry for the delay, we were checking this in driver also. The issue was due to a delay in workqueue scheduling, caused by msleep() inside driver. Because of this, last transmission happens long after the dynamic power save timer is scheduled. So, the difference between last transmission time and the time it goes to sleep is less than the defined PSM timeout period. I think that this patch might be considered as a workaround for such delays caused by driver as long as it not creating any other issues. saravanan. ________________________________________ From: ext John W. Linville [linville@xxxxxxxxxxxxx] Sent: Monday, March 29, 2010 8:55 PM To: Johannes Berg Cc: Dhanabal Saravanan (EXT-Sasken/Tampere); linux-wireless@xxxxxxxxxxxxxxx Subject: Re: [PATCH] mac80211: Reschedule dynamic power save timer after wakeup On Wed, Mar 17, 2010 at 09:01:08AM -0700, Johannes Berg wrote: > On Wed, 2010-03-17 at 12:09 +0100, ext-saravanan.dhanabal@xxxxxxxxx > wrote: > > In worst case it takes up to that much, though the average is less but still significant. > > > On Tue, 2010-03-16 at 11:31 -0400, Saravanan Dhanabal wrote: > > > After last transmission, the device goes to sleep earlier > > > than the configured dynamic power save timeout. If timeout > > > is set to 400ms, device enters into sleep mode at around > > > 330ms since from last TX. > > I still don't think I understand this patch. Why would you be interested > in the exact timing rather than the time since the transmission? I > mean ... why does it go to sleep _earlier_? Any further comments on this one? John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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
