Commit 5d6ce628 authored by Bob Copeland's avatar Bob Copeland Committed by John W. Linville

ath5k: dont use external sleep clock in AP mode

When using the external sleep clock in AP mode, the
TSF increments too quickly, causing beacon interval
to be much lower than it is supposed to be, resulting
in lots of beacon-not-ready interrupts.

This fixes http://bugzilla.kernel.org/show_bug.cgi?id=14802.
Signed-off-by: default avatarBob Copeland <me@bobcopeland.com>
Acked-by: default avatarNick Kossifidis <mickflemm@gmail.com>
Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
parent d0dd2de0
...@@ -1374,8 +1374,9 @@ int ath5k_hw_reset(struct ath5k_hw *ah, enum nl80211_iftype op_mode, ...@@ -1374,8 +1374,9 @@ int ath5k_hw_reset(struct ath5k_hw *ah, enum nl80211_iftype op_mode,
* Set clocks to 32KHz operation and use an * Set clocks to 32KHz operation and use an
* external 32KHz crystal when sleeping if one * external 32KHz crystal when sleeping if one
* exists */ * exists */
if (ah->ah_version == AR5K_AR5212) if (ah->ah_version == AR5K_AR5212 &&
ath5k_hw_set_sleep_clock(ah, true); ah->ah_op_mode != NL80211_IFTYPE_AP)
ath5k_hw_set_sleep_clock(ah, true);
/* /*
* Disable beacons and reset the register * Disable beacons and reset the register
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment