From: Felix Fietkau <nbd@openwrt.org>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
rodrigue@qca.qualcomm.com
Subject: Re: [PATCH 3.6 4/4] ath9k_hw: enable PA linearization
Date: Wed, 08 Aug 2012 17:12:25 +0200 [thread overview]
Message-ID: <502281D9.4030109@openwrt.org> (raw)
In-Reply-To: <20120808145531.GB2041@vmraj-lnx.qualcomm.com>
On 2012-08-08 4:55 PM, Rajkumar Manoharan wrote:
> On Tue, Aug 07, 2012 at 03:06:12PM +0200, Felix Fietkau wrote:
>> This feature had been disabled in ath9k because the code to support
>> it was incomplete, but now the code is in sync with the internal QCA
>> codebase, so it's time to enable it.
>>
>> On many newer devices, the calibration is assumed to be done with PA
>> linearization enabled.
>>
>> Tests with a particular AR933x device showed that the signal emitted
>> at full power was highly distorted and unreliable with PA linearization
>> disabled. With this patch, the signal becomes clear and stability
>> is improved.
>>
> We faced stability issues with 938x chipsets when paprd is enabled. The commit
> 6f4810101a629b31b5427872a09ea092cfc5c4bd states one of the issue. Even if it
> helps for AR933x, let us enable it only for that chip alone.
That was in January 2011, lots of bugs have been fixed since then,
initvals have been updated, EEPROM code has changed, ...
The internal QCA codebase enables PAPRD for all AR93xx devices that
support it, meaning non-PAPRD tx receives much less test coverage there.
While this issue has only been visible on a particular AR933x device, I
believe this is not the only one that's going to be affected, as the
EEPROM of any new device is calibrated for PAPRD-enabled operation.
If you don't want to enable it now, when do you think would be the right
time to enable it? Before I sent this patch, I did a detailed code
review to make sure that any obvious code discrepancies in PAPRD between
the internal codebase and ath9k are dealt with.
What else is needed to get this issue sorted out?
- Felix
next prev parent reply other threads:[~2012-08-08 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 13:06 [PATCH 3.6 1/4] ath9k_hw: do not enable the MIB interrupt in the interrupt mask register Felix Fietkau
2012-08-07 13:06 ` [PATCH 3.6 2/4] ath9k_hw: clear the AM2PM predistortion mask on AR933x Felix Fietkau
2012-08-07 13:06 ` [PATCH 3.6 3/4] ath9k_hw: calibrate PA input for PA predistortion Felix Fietkau
2012-08-07 13:06 ` [PATCH 3.6 4/4] ath9k_hw: enable PA linearization Felix Fietkau
2012-08-08 14:17 ` Mohammed Shafi
2012-08-08 14:23 ` Felix Fietkau
2012-08-08 14:55 ` Rajkumar Manoharan
2012-08-08 15:12 ` Felix Fietkau [this message]
2012-08-08 15:29 ` Rajkumar Manoharan
2012-08-10 18:44 ` John W. Linville
2012-08-09 4:45 ` Mohammed Shafi
2012-08-10 16:14 ` Sujith Manoharan
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=502281D9.4030109@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rmanohar@qca.qualcomm.com \
--cc=rodrigue@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 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).