Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit e576defd authored by Thomas Pedersen's avatar Thomas Pedersen Committed by John W. Linville
Browse files

ath5k: RX timestamp is reported at end of frame 



This is true for at least AR5213, and shouldn't be different for other
ath5k PHYs. Tested on AR2413 and AR5414.

Signed-off-by: default avatarThomas Pedersen <thomas@cozybit.com>
Tested-by: default avatarBob Copeland <me@bobcopeland.com>
Acked-by: default avatarNick Kossifidis <mickflemm@gmail.com>
Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
parent 75d7dbc2

drivers/net/wireless/ath/ath5k/base.c

+1 −12
Original line number Diff line number Diff line
@@ -1336,20 +1336,9 @@ ath5k_receive_frame(struct ath5k_hw *ah, struct sk_buff *skb, 
	 * 15bit only. that means TSF extension has to be done within

	 * 32768usec (about 32ms). it might be necessary to move this to

	 * the interrupt handler, like it is done in madwifi.

	 *

	 * Unfortunately we don't know when the hardware takes the rx

	 * timestamp (beginning of phy frame, data frame, end of rx?).

	 * The only thing we know is that it is hardware specific...

	 * On AR5213 it seems the rx timestamp is at the end of the

	 * frame, but I'm not sure.

	 *

	 * NOTE: mac80211 defines mactime at the beginning of the first

	 * data symbol. Since we don't have any time references it's

	 * impossible to comply to that. This affects IBSS merge only

	 * right now, so it's not too bad...

	 */

	rxs->mactime = ath5k_extend_tsf(ah, rs->rs_tstamp);

	rxs->flag |= RX_FLAG_MACTIME_START;

	rxs->flag |= RX_FLAG_MACTIME_END;



	rxs->freq = ah->curchan->center_freq;

	rxs->band = ah->curchan->band;