diff options
author | Sujith Manoharan <c_manoha@qca.qualcomm.com> | 2014-09-11 19:05:48 +0530 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2014-09-11 14:17:20 -0400 |
commit | ae0fd6354134e63aa3e62456e2080c430287144d (patch) | |
tree | 1eeaa4174e1c1379a99ccf3305f17a36e6d50b56 /net/x25 | |
parent | 3b924ea1ac55caca853992b425a56513d74d67dc (diff) | |
download | linux-ae0fd6354134e63aa3e62456e2080c430287144d.tar.bz2 |
Revert "ath9k: Calculate sleep duration"
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.
Cc: stable@vger.kernel.org
Cc: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/x25')
0 files changed, 0 insertions, 0 deletions