ath10k: remove tsf argument from rx_desc tracing
authorMichal Kazior <michal.kazior@tieto.com>
Thu, 23 Oct 2014 14:04:27 +0000 (17:04 +0300)
committerKalle Valo <kvalo@qca.qualcomm.com>
Fri, 24 Oct 2014 13:33:20 +0000 (16:33 +0300)
commitb04e204fcae5a2c1e99e94f7e80f1e75fa95b938
tree982dcd6d7d96f31ec1bcbf7cdba7e74eb5517083
parent51fc7d74ce4a1d92623e592eff14403872fb26bd
ath10k: remove tsf argument from rx_desc tracing

Fundamentally this was wrong. Tsf is only valid
in last MPDU of a PPDU. This means tsf value was
wrong most of the time during heavy traffic.

Also I don't see much point in exposing a
redundant (and broken) tsf value. Userspace can
already read it from the dumped rx descriptor
buffer.

Cc: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
drivers/net/wireless/ath/ath10k/htt_rx.c
drivers/net/wireless/ath/ath10k/trace.h