Return-path: Received: from nbd.name ([46.4.11.11]:45003 "EHLO nbd.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754232Ab2DRTwH (ORCPT ); Wed, 18 Apr 2012 15:52:07 -0400 Message-ID: <4F8F1B5F.7050603@openwrt.org> (sfid-20120418_215211_872078_3AFEF6E5) Date: Wed, 18 Apr 2012 21:51:59 +0200 From: Felix Fietkau MIME-Version: 1.0 To: Gabor Juhos CC: "John W. Linville" , linux-wireless@vger.kernel.org, "ath9k-devel@lists.ath9k.org" Subject: Re: [RFC] ath9k: fix TX power reporting on AR9003 chips References: <1334740589-7853-1-git-send-email-juhosg@openwrt.org> In-Reply-To: <1334740589-7853-1-git-send-email-juhosg@openwrt.org> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 2012-04-18 11:16 AM, Gabor Juhos wrote: > 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 Acked-by: Felix Fietkau