On Thu, Sep 11, 2014 at 07:05:48PM +0530, Sujith Manoharan wrote: > From: Sujith Manoharan <c_manoha@xxxxxxxxxxxxxxxx> > > This reverts commit 09ebb810927a110e4c354beb20308830d108a54b. > > ath9k_hw_set_sta_beacon_timers() configures AR_TIM_PERIOD with > the beacon interval. Before this commit, the sleepduration was > never greater than the beacon interval. But now, the behavior > has changed. For example, with an AP that uses a beacon interval of 100: > > ath: phy9: next beacon 61128704 > ath: phy9: beacon period 204800 > ath: phy9: DTIM period 204800 > > If the sleepduration is calculated based on the listen time, then > the bmiss threshold should also be changed since the HW would > be in sleep state for a longer time, but that is not done currently. > > To avoid configuring a higher beacon interval based on the sleepduration, > revert to the original behavior. Power consumption is not a > problem since PS is disabled in ath9k anyway. > Some of the IOE customer using ath9k with power save enabled. IIRC the expectation is that when the station is idle, it should wakeup on DTIM beacon not for every beacons. Are you seeing frequest bmiss events on higher beacon interval? -Rajkumar -- 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
