From: Felix Fietkau <nbd@openwrt.org>
To: Vasanthakumar Thiagarajan <vasanth@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Senthil Balasubramanian <senthilkumar@atheros.com>
Subject: Re: [PATCH 01/11] ath9k_hw: Fix a reset failure on AR9382 (2x2).
Date: Wed, 10 Nov 2010 17:23:22 +0100 [thread overview]
Message-ID: <4CDAC6FA.1000003@openwrt.org> (raw)
In-Reply-To: <1289394196-3465-1-git-send-email-vasanth@atheros.com>
On 2010-11-10 2:03 PM, Vasanthakumar Thiagarajan wrote:
> From: Senthil Balasubramanian <senthilkumar@atheros.com>
>
> AR9382 needs to be configured for the correct chain mask before
> running AGC/TxIQ caliberation. Otherwise reset would fail.
>
> Signed-off-by: Senthil Balasubramanian <senthilkumar@atheros.com>
> ---
> drivers/net/wireless/ath/ath9k/ar9003_calib.c | 7 +++++++
> drivers/net/wireless/ath/ath9k/reg.h | 2 ++
> 2 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/ar9003_calib.c b/drivers/net/wireless/ath/ath9k/ar9003_calib.c
> index 9e6edff..ba898f2 100644
> --- a/drivers/net/wireless/ath/ath9k/ar9003_calib.c
> +++ b/drivers/net/wireless/ath/ath9k/ar9003_calib.c
> @@ -718,7 +718,14 @@ static bool ar9003_hw_init_cal(struct ath_hw *ah,
> struct ath9k_channel *chan)
> {
> struct ath_common *common = ath9k_hw_common(ah);
> + int val;
>
> + val = REG_READ(ah, AR_ENT_OTP);
> + ath_print(common, ATH_DBG_CALIBRATE, "ath9k: AR_ENT_OTP 0x%x\n", val);
> +
> + if (val & AR_ENT_OTP_CHAIN2_DISABLE)
> + ar9003_hw_set_chain_masks(ah, 0x3, 0x3);
> + else
> /*
> * 0x7 = 0b111 , AR9003 needs to be configured for 3-chain mode before
> * running AGC/TxIQ cals
This messes up the code formatting, the lines after that need some
indenting.
- Felix
prev parent reply other threads:[~2010-11-10 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 13:03 [PATCH 01/11] ath9k_hw: Fix a reset failure on AR9382 (2x2) Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 02/11] ath9k_hw: Add new member into the eeprom structure Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 03/11] ath9k_hw: Initialize 2GHz CTL properly Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 04/11] ath9k_hw: Fix paprd training frame failure Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 05/11] ath9k_hw: add eeprom templates for ar9003 family chipsets Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 06/11] ath9k_hw: Fix XPABIAS level configuration for AR9003 Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 07/11] ath9k_hw: Enable strong signal detection " Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 08/11] ath9k_hw: Improve power control accuracy " Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 09/11] ath9k_hw: Add helper function for interpolation Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 10/11] ath9k: Fix bug in delimiter padding computation Vasanthakumar Thiagarajan
2010-11-10 13:03 ` [PATCH 11/11] ath9k_hw: Fix low throughput issue with AR93xx Vasanthakumar Thiagarajan
2010-11-10 16:23 ` Felix Fietkau [this message]
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=4CDAC6FA.1000003@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=senthilkumar@atheros.com \
--cc=vasanth@atheros.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).