diff options
author | 2015-10-20 14:19:26 +0200 | |
---|---|---|
committer | 2015-10-28 20:57:13 +0200 | |
commit | 56bae464275ac57cbf993f3ed15e96d6e1ec00a2 (patch) | |
tree | 09636ae24ad9c3a10d0b681a52ba13b552912906 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | orinoco_usb: return error in ezusb_probe when alloc_orinocodev fails (diff) | |
download | wireguard-linux-56bae464275ac57cbf993f3ed15e96d6e1ec00a2.tar.xz wireguard-linux-56bae464275ac57cbf993f3ed15e96d6e1ec00a2.zip |
ath9k: fix phyerror codes
Some of the ath9k_phyerr enums were wrong from the
beginning (and even before). Most of the time the
codes were used for counters to be displayed over
debugfs, which made this a non-functional issue.
Some (e.g. ATH9K_PHYERR_FALSE_RADAR_EXT) are used
for radar detection and require the correct code
to work as intended.
This patch includes:
a) fixes
ATH9K_PHYERR_FALSE_RADAR_EXT: 24 => 36
ATH9K_PHYERR_CCK_LENGTH_ILLEGAL: 32 => 28
ATH9K_PHYERR_CCK_POWER_DROP: 33 => 29
ATH9K_PHYERR_HT_CRC_ERROR: 34 => 32
ATH9K_PHYERR_HT_LENGTH_ILLEGAL: 35 => 33
ATH9K_PHYERR_HT_RATE_ILLEGAL: 36 => 34
b) extensions
ATH9K_PHYERR_CCK_BLOCKER = 24
ATH9K_PHYERR_HT_ZLF = 35
ATH9K_PHYERR_GREEN_FIELD = 37
Aside from the correction and completion made in
the enum, the patch also extends the display of
the related counters in the debugfs.
Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions