linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohammed Shafi <mshajakhan@atheros.com>
To: Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Cc: Mohammed Shajakhan <Mohammed.Shajakhan@Atheros.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	Senthilkumar Balasubramanian
	<Senthilkumar.Balasubramanian@Atheros.com>
Subject: Re: [RFC/RFT 4/9] ath9k_hw: config diversity based on eeprom contents
Date: Fri, 29 Apr 2011 10:22:11 +0530	[thread overview]
Message-ID: <4DBA43FB.6010709@atheros.com> (raw)
In-Reply-To: <20110428173944.GB29252@tux>

On Thursday 28 April 2011 11:09 PM, Luis Rodriguez wrote:
> On Thu, Apr 28, 2011 at 07:22:54AM -0700, Mohammed Shajakhan wrote:
>    
>> From: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
>>
>> * enable LNA-diversity, fast-diversity based on the value read from
>>    EEPROM content
>> * if antenna diversity/combining is supported set LNA1 for the main
>>    antenna and LNA2 for the alternate antenna based on the new diversity
>>    algorithm
>>      
> The commit log does not mention this is specifically only for
> AR9485. Adding this can help reviewers / distributions.
>    
Ok Luis, I will address that.

thanks,
shafi
>    Luis
> .
>
>    

  reply	other threads:[~2011-04-29  4:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 14:22 [RFC/RFT 0/9] ath9k: Add Antenna diversity support for AR9485 Mohammed Shafi Shajakhan
2011-04-28 14:22 ` [RFC/RFT 1/9] ath9k_hw: make antenna diversity modules chip specific Mohammed Shafi Shajakhan
2011-04-29  4:10   ` Vasanthakumar Thiagarajan
2011-04-29  5:21     ` Mohammed Shafi
2011-04-28 14:22 ` [RFC/RFT 2/9] ath9k_hw: enable Antenna diversity for AR9485 Mohammed Shafi Shajakhan
2011-04-28 14:22 ` [RFC/RFT 3/9] ath9k_hw: define registers/macros to support Antenna diversity Mohammed Shafi Shajakhan
2011-04-29  4:20   ` Vasanthakumar Thiagarajan
2011-04-29  4:53     ` Mohammed Shafi
2011-04-28 14:22 ` [RFC/RFT 4/9] ath9k_hw: config diversity based on eeprom contents Mohammed Shafi Shajakhan
2011-04-28 17:39   ` Luis R. Rodriguez
2011-04-29  4:52     ` Mohammed Shafi [this message]
2011-04-29  4:43   ` Vasanthakumar Thiagarajan
2011-04-29  6:34     ` Mohammed Shafi
2011-04-29  6:49     ` Mohammed Shafi
2011-04-28 14:22 ` [RFC/RFT 5/9] ath9k_hw: define modules to get/set Antenna diversity paramaters Mohammed Shafi Shajakhan
2011-04-28 14:22 ` [RFC/RFT 6/9] ath9k_hw: define antenna diversity group Mohammed Shafi Shajakhan
2011-04-28 14:22 ` [RFC/RFT 7/9] ath9k: Implement an API to swap main/ALT LNA's Mohammed Shafi Shajakhan
2011-04-28 14:22 ` [RFC/RFT 8/9] ath9k: configure fast_div_bias based on diversity group Mohammed Shafi Shajakhan
2011-04-28 14:22 ` [RFC/RFT 9/9] ath9k: make sure main_rssi is positive Mohammed Shafi Shajakhan
2011-04-28 18:12 ` [RFC/RFT 0/9] ath9k: Add Antenna diversity support for AR9485 Luis R. Rodriguez
2011-04-28 18:12   ` Luis R. Rodriguez
2011-04-29  4:52     ` Mohammed Shafi
2011-05-12 16:59       ` John W. Linville
2011-05-13  4:22         ` Mohammed Shafi

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=4DBA43FB.6010709@atheros.com \
    --to=mshajakhan@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Mohammed.Shajakhan@Atheros.com \
    --cc=Senthilkumar.Balasubramanian@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).