ath5k: use 3 instead of 0x00000003
reviewed beacon timer initialization with register traces from madwifi: what we are doing is correct :). one minor fix: use 3 instead of 0x00000003 - it's more readable. drivers/net/wireless/ath5k/hw.c: Changes-licensed-under: ISC Signed-off-by: Bruno Randolf <bruno@thinktube.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
parent
1f7d87b0ec
commit
1008e0f7b9
|
@ -2605,10 +2605,8 @@ void ath5k_hw_init_beacon(struct ath5k_hw *ah, u32 next_beacon, u32 interval)
|
|||
break;
|
||||
|
||||
default:
|
||||
timer1 = (next_beacon - AR5K_TUNE_DMA_BEACON_RESP) <<
|
||||
0x00000003;
|
||||
timer2 = (next_beacon - AR5K_TUNE_SW_BEACON_RESP) <<
|
||||
0x00000003;
|
||||
timer1 = (next_beacon - AR5K_TUNE_DMA_BEACON_RESP) << 3;
|
||||
timer2 = (next_beacon - AR5K_TUNE_SW_BEACON_RESP) << 3;
|
||||
}
|
||||
|
||||
timer3 = next_beacon + (ah->ah_atim_window ? ah->ah_atim_window : 1);
|
||||
|
|
Loading…
Reference in New Issue