diff options
| author | Gabor Juhos <juhosg@openwrt.org> | 2012-04-18 22:23:38 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2012-04-23 15:34:06 -0400 |
| commit | 75acd5a82afda30fb615335ff6c8e5f3a1ca5e83 (patch) | |
| tree | 640d28f99e4eb1f9dfb45e6f3468b8541224bc03 /drivers/net/tun.c | |
| parent | 488c3ee77ea0e63c9ae4736b1610aaf39c6527ee (diff) | |
| download | linux-3.10-75acd5a82afda30fb615335ff6c8e5f3a1ca5e83.tar.gz linux-3.10-75acd5a82afda30fb615335ff6c8e5f3a1ca5e83.tar.bz2 linux-3.10-75acd5a82afda30fb615335ff6c8e5f3a1ca5e83.zip | |
ath9k: fix TX power reporting on AR9003 chips
The current code unconditionally reads the target
power values for all modes from the EEPROM. However
In 'ar9003_hw_set_power_per_rate_table' the regulatory
caps are applied only on a mode specific subset of the
power values.
The reported TX power level is calculated from the
maximum of the power values. Because some of these
values are uncapped in certain cases, the reported
TX power will be wrong.
On the older chipset, we don't have such problems
because only the mode specific subset of the power
levels are retrieved from the EEPROM on those. Do
the same for the AR9003 chips to fix the issue.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
Acked-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/tun.c')
0 files changed, 0 insertions, 0 deletions