diff options
| author | Michal Kazior <michal.kazior@tieto.com> | 2014-10-23 17:04:27 +0300 |
|---|---|---|
| committer | Kalle Valo <kvalo@qca.qualcomm.com> | 2014-10-24 16:33:20 +0300 |
| commit | b04e204fcae5a2c1e99e94f7e80f1e75fa95b938 (patch) | |
| tree | 982dcd6d7d96f31ec1bcbf7cdba7e74eb5517083 /tools/perf/scripts/python | |
| parent | 51fc7d74ce4a1d92623e592eff14403872fb26bd (diff) | |
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>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions