ath9k: Optimize TBTT/DTIM calculation for timers
authorJouni Malinen <jouni.malinen@atheros.com>
Wed, 20 May 2009 18:56:39 +0000 (21:56 +0300)
committerJohn W. Linville <linville@tuxdriver.com>
Fri, 22 May 2009 18:06:01 +0000 (14:06 -0400)
commit267a90127472be70b02ab13cbd355b5013e2aa51
tree916825c0db1c68751ad280a54ee65e03395821c6
parentd26285f873c3066fefe648b47b9ecf3ec18bcfbc
ath9k: Optimize TBTT/DTIM calculation for timers

The previous version used a simple loop to go through all Beacon
frames when determining the next TBTT and DTIM count. This is not too
bad for the case where the setup happens before timesync (i.e., very
small TSF), but this can become very heavy operation if a short Beacon
interval is used and the current TSF is large.

In preparation for a patch to update timer setup based on Beacon
timestamp, optimize this routine to take fixed time regardless of the
actual TSF value.

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