diff options
author | Benjamin Berg <benjamin.berg@open-mesh.com> | 2016-07-04 14:37:20 +0200 |
---|---|---|
committer | Kalle Valo <kvalo@qca.qualcomm.com> | 2016-07-08 17:03:20 +0300 |
commit | fa5106e1d79382fc3181524902a92b813e57a56d (patch) | |
tree | 79c4709847b9000c9dae529dc5ce7ddff7e28d22 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 28755b8f6d94a51810f68e1dfe302309ce452719 (diff) |
ath9k: Correct TSF adjustment to align the beacon time correctly
Beacons were not send out at (timestamp % beacon_time == 0) for interfaces
other than the primary one. To send out beacons with the correct timestamp
according to 10.1.3.2 of the 802.11 standard the tsf_adjustment has to be
set to the negative time difference instead of positive. This way the
later beacons get corrected to have a lower (and similar) timestamp with
regard to the beacon from slot 0.
I am not aware about any issues that have been caused by this.
Signed-off-by: Benjamin Berg <benjamin.berg@open-mesh.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions