From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC] ath9k: fix TX power reporting on AR9003 chips
Date: Wed, 18 Apr 2012 21:51:59 +0200 [thread overview]
Message-ID: <4F8F1B5F.7050603@openwrt.org> (raw)
In-Reply-To: <1334740589-7853-1-git-send-email-juhosg@openwrt.org>
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 <juhosg@openwrt.org>
Acked-by: Felix Fietkau <nbd@openwrt.org>
WARNING: multiple messages have this Message-ID (diff)
From: Felix Fietkau <nbd@openwrt.org>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: Re: [RFC] ath9k: fix TX power reporting on AR9003 chips
Date: Wed, 18 Apr 2012 21:51:59 +0200 [thread overview]
Message-ID: <4F8F1B5F.7050603@openwrt.org> (raw)
In-Reply-To: <1334740589-7853-1-git-send-email-juhosg@openwrt.org>
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 <juhosg@openwrt.org>
Acked-by: Felix Fietkau <nbd@openwrt.org>
next prev parent reply other threads:[~2012-04-18 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 9:16 [ath9k-devel] [RFC] ath9k: fix TX power reporting on AR9003 chips Gabor Juhos
2012-04-18 9:16 ` Gabor Juhos
2012-04-18 19:51 ` Felix Fietkau [this message]
2012-04-18 19:51 ` Felix Fietkau
2012-04-18 20:19 ` [ath9k-devel] " Gabor Juhos
2012-04-18 20:19 ` Gabor Juhos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F8F1B5F.7050603@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.