On 02/20/2012 03:38 PM, rmani@xxxxxxxxxxxxxxxx wrote: > From: Raja Mani <rmani@xxxxxxxxxxxxxxxx> > > Firmware has the option to support the listen interval > per vif specific. Fix this. > > Listen interval can be set by the TUs or by the number > of beacons. Current code enables the user to configure > the listen interval in the unit of 'number of beacons' > using debugfs entry "listen_interval". Going forward, > we need to alter the listen interval in the unit of TUs > to get good power numbers while going to WOW suspend/resume. > > Allowing the user to change the listen interval in > the unit of "number of beacons" in debugfs and changing > listen interval in wow suspend/resume in the unit of > time (TUs) would lead us to confuse. > > This patch make sures the listen interval is changed only > in the unit of time (TUs). > > Signed-off-by: Raja Mani <rmani@xxxxxxxxxxxxxxxx> I think these two patches depend on your 'ath6kl: Check wow state before sending control and data pkt'? At least I got conflicts and they seem to point to that patch. If that's the case, I'll put these two patches on hold until the other patch is applied. 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
