ath9k: Update Beacon timers based on timestamp from the AP
authorJouni Malinen <jouni.malinen@atheros.com>
Wed, 20 May 2009 18:59:08 +0000 (21:59 +0300)
committerJohn W. Linville <linville@tuxdriver.com>
Fri, 22 May 2009 18:06:01 +0000 (14:06 -0400)
commitccdfeab6536ae55d43436ffaae949afde6e962ca
treedf00994be9edcaf8e8fd4d97ebafe74e710722d5
parent267a90127472be70b02ab13cbd355b5013e2aa51
ath9k: Update Beacon timers based on timestamp from the AP

Some APs seem to drift away from the expected TBTT (timestamp %
beacon_int_in_usec differs quite a bit from zero) which can result in
us waking up way too early to receive a Beacon frame. In order to work
around this, re-configure the Beacon timers after having received a
Beacon frame from the AP (i.e., when we know the offset between the
expected TBTT and the actual time the AP is sending out the Beacon
frame).

Signed-off-by: Jouni Malinen <jouni.malinen@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/ath/ath9k/ath9k.h
drivers/net/wireless/ath/ath9k/main.c
drivers/net/wireless/ath/ath9k/recv.c