linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Mark Mentovai <mark@moxienet.com>, linux-wireless@vger.kernel.org
Subject: Re: ath9k max_power question
Date: Thu, 11 Nov 2010 20:31:12 +0100	[thread overview]
Message-ID: <4CDC4480.8050206@openwrt.org> (raw)
In-Reply-To: <AANLkTimVEm7=c-fof_niToJqy1t+C5fk_JYH_=x1+p5r@mail.gmail.com>

On 2010-11-11 8:22 PM, Luis R. Rodriguez wrote:
> On Thu, Nov 11, 2010 at 11:15 AM, Mark Mentovai <mark@moxienet.com> wrote:
>> In drivers/net/wireless/ath/ath9k/init.c, both CHAN2G and CHAN5G set
>> .max_power to 20, represented in dBm. I’m wondering how this number
>> was chosen. Is it simply a safe generic value? I’m dealing with a
>> device on which the vendor’s madwifi-based binary driver would show
>> 23dBm for 2.4GHz and 18dBm for 5GHz (although only when I asked it for
>> 26dBm and 24dBm respectively, so I’m not sure which set of numbers to
>> believe.)
>>
>> I noticed that in ath9k, if these .max_power limits are raised, the
>> driver is happy to set a somewhat higher transmit power. In this case,
>> it will max out at 25dBm for 2.4GHz and 21dBm for 5GHz. These are
>> still below the relevant regulatory limits. These values seem to be
>> computed by routines in eeprom_*.c, so I’m wondering if they’re based
>> on the card’s own data and safe to use without fear of burning the
>> radios.
> 
> The values are just some safe value to use as defaults but will
> quickly be replaced by the max regulatory allowed and then upon
> further inspection also capped to the lower value of the regulatory
> limit, the max allowed device limit (where things start becoming
> unreliable), and the CTL indexed limit which is calibrated
> specifically for the card you use, so this will vary. You can read
> more about it here:
> 
> http://wireless.kernel.org/en/users/Drivers/ath
That should have already been taken care of by this commit (w-t):

commit 6cdd07721180145b7ef46bd63f1eee636983f0e6
Author: Felix Fietkau <nbd@openwrt.org>
Date:   Wed Oct 20 02:09:46 2010 +0200

ath9k: initialize per-channel tx power limits instead of hardcoding them


- Felix

  reply	other threads:[~2010-11-11 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 19:15 ath9k max_power question Mark Mentovai
2010-11-11 19:22 ` Luis R. Rodriguez
2010-11-11 19:31   ` Felix Fietkau [this message]
2010-11-16 19:24     ` Mark Mentovai

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=4CDC4480.8050206@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mark@moxienet.com \
    --cc=mcgrof@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).