mirror of
https://github.com/torvalds/linux.git
synced 2024-11-20 11:01:38 +00:00
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: Thomas Pedersen <thomas@cozybit.com> Tested-by: Bob Copeland <me@bobcopeland.com> Acked-by: Nick Kossifidis <mickflemm@gmail.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
parent
75d7dbc280
commit
e576defd1f
@ -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
|
* 15bit only. that means TSF extension has to be done within
|
||||||
* 32768usec (about 32ms). it might be necessary to move this to
|
* 32768usec (about 32ms). it might be necessary to move this to
|
||||||
* the interrupt handler, like it is done in madwifi.
|
* 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->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->freq = ah->curchan->center_freq;
|
||||||
rxs->band = ah->curchan->band;
|
rxs->band = ah->curchan->band;
|
||||||
|
Loading…
Reference in New Issue
Block a user