All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	Paul Stewart <pstew@google.com>,
	Adrian Chadd <adrian.chadd@gmail.com>
Subject: Re: [PATCH v2 4/4] ath9k_hw: Fix tx power settings for AR9003
Date: Thu, 10 Nov 2011 17:17:14 +0100	[thread overview]
Message-ID: <4EBBF90A.2000808@openwrt.org> (raw)
In-Reply-To: <4EBBA1C4.3070007@openwrt.org>

On 2011-11-10 11:04 AM, Felix Fietkau wrote:
> On 2011-11-10 10:44 AM, Rajkumar Manoharan wrote:
>>  Retriving tx power for 2x2 and 3x3 chainmask is not handled
>>  properly. While calculating tx power for 2x2, 3 dBm was reduced
>>  and for 3x3, 5 dBm was reduced which should be added back when
>>  retriving.
>>
>>  Cc: Paul Stewart<pstew@google.com>
>>  Signed-off-by: Rajkumar Manoharan<rmanohar@qca.qualcomm.com>
> I think the tx power reduction for 2x2/3x3 needs to be revisited. In the
> discussion that led to Walsh spatial spreading being disabled you
> mentioned this:
>
>>  In the FCC rulings, only transmissions that are completely non-coherent, are
>>  allowed to waive the array gain contribution to EIRP for multi-transmit configurations.
>>  The use of 2-stream with 2 transmit and use of 3-steam with 3 transmit qualifies
>>  for this spatial multiplexing MIMO classification as long as the streams are
>>  directly mapped to each radio (not Walsh spread prior to splitting to multiple radios)
> So if I understand this issue correctly, Walsh spatial spreading was
> disabled so that the tx power for 2x2 or 3x3 would not have to be
> reduced by the array gain contribution - yet we're still doing that.
>
> When Adrian pointed out that tx power is reduced based on the number of
> chains, you mentioned this:
>>  Those pwrdecrease fields are applicable for AR9280 chips not for AR9003.
>
> According to this patch, this doesn't seem to match what the code does,
> though I didn't notice it back then.
>
> So before we merge this patch, let's decide whether we actually need
> this tx power reduction or not.
I just spent some time reading up on the FCC's MIMO test procedures and 
it appears that I just got mixed up in the terminology earlier. The 
patch should be merged as-is.

- Felix

  reply	other threads:[~2011-11-10 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10  9:44 [PATCH v2 4/4] ath9k_hw: Fix tx power settings for AR9003 Rajkumar Manoharan
2011-11-10 10:04 ` Felix Fietkau
2011-11-10 16:17   ` Felix Fietkau [this message]
     [not found]     ` <CALSq=BbAG_aJ=p10cHdmQVYTMpfdRwf6sTPEAaFrrrDJCmNW4Q@mail.gmail.com>
2011-12-05 18:14       ` Fwd: " Daniel Halperin

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=4EBBF90A.2000808@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=adrian.chadd@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=pstew@google.com \
    --cc=rmanohar@qca.qualcomm.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 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.