Lines Matching full:tsf

46  * - Maintaining TSF
50  * - Updating beacon data (with TSF etc)
556  * ath5k_hw_get_tsf64() - Get the full 64bit TSF
559  * Returns the current TSF
572 	 * While reading TSF upper and then lower part, the clock is still  in ath5k_hw_get_tsf64()
602  * ath5k_hw_set_tsf64() - Set a new 64bit TSF
604  * @tsf64: The new 64bit TSF
606  * Sets the new TSF
616  * ath5k_hw_reset_tsf() - Force a TSF reset
619  * Forces a TSF reset on PCU
630 	 * signal to reset TSF, but if left high it will cause a TSF reset  in ath5k_hw_reset_tsf()
692 	/* When in AP or Mesh Point mode zero timer0 to start TSF */  in ath5k_hw_init_beacon_timers()
702 	/* Force a TSF reset if requested and enable beacons */  in ath5k_hw_init_beacon_timers()
767  * separately based on the current TSF value. The hardware increments each
768  * timer by the beacon interval, when the local TSF converted to TU is equal
771  * The reception of a beacon with the same BSSID can update the local HW TSF
772  * at any time - this is something we can't avoid. If the TSF jumps to a
774  * be updated until the TSF in TU wraps around at 16 bit (the size of the
778  * that they define a time "window". When the TSF jumps between two timers
781  * interval. This causes the window to get larger, until the TSF wraps