ath5k: dont use external sleep clock in AP mode
authorBob Copeland <me@bobcopeland.com>
Thu, 11 Mar 2010 23:23:48 +0000 (18:23 -0500)
committerGreg Kroah-Hartman <gregkh@suse.de>
Thu, 1 Apr 2010 22:58:07 +0000 (15:58 -0700)
commitd69b8a11c138141bf2ee5f0d218111e923061a62
treef1288ec5102943331addf7b31bba556ff38f1856
parentcde4ff84e046eaed345bde28aa2e5529b5124d02
ath5k: dont use external sleep clock in AP mode

commit 5d6ce628f986d1a3c523cbb0a5a52095c48cc332 upstream

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: Bob Copeland <me@bobcopeland.com>
Acked-by: Nick Kossifidis <mickflemm@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Cc: Luis Rodriguez <lrodriguez@atheros.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/net/wireless/ath/ath5k/reset.c