All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: Problems with diversity on AR9330
Date: Fri, 06 Jul 2012 17:13:42 +0200	[thread overview]
Message-ID: <5244861.J1Tyef1FCX@bentobox> (raw)
In-Reply-To: <CAD2nsn1=PDBTRXumDh93DzvmFcBnyFeLD-5c5oSJmv3OO6LWGw@mail.gmail.com>

On Friday 06 July 2012 19:32:41 Mohammed Shafi wrote:
> Hi Simon,
> 
> On Fri, Jul 6, 2012 at 6:20 PM, Simon Wunderlich
> 
> <simon.wunderlich@s2003.tu-chemnitz.de> wrote:
> > Hey,
> > 
> > we have trouble with an AR9330 (Hornet) based AP. This device has 2
> > antennas, and is supposed to support diversity (2 RX, 1 TX). However,
> > diversity is not really enabled because the "alternative" antenna is not
> > considered as "good", because not enough frames are received. It seems
> > that at 99% of the time, alt_rssi (read from rs->rs_rssi_ctl1) is invalid
> > (set to ATH9K_RSSI_BAD, -128), while main_rssi (read from
> > rs->rs_rssi_ctl0) usually has sane values.
> its been some good amount of time i had taken/tested take a look at
> this. actually Gabor Juhos added the support for AR9330.
> seems AR9003 family chipsets can exhibit this behaviour. i quickly
> checked with AR9285(AR9002) which seems to have a positive RSSI
> regulary in ctl0/ctl1.
> i also have a AR9485(AR9003 family) which might be similar to AR9330.
> just checked with removing the antenna in chain0 seems to bring
> positive values in rssi_ctl1.
> I just also observer the chain0 is "preferred" unless the RSSI is so
> poor in it so chain1 is taken.
> Please check if this work out for your case too.

Removing the antenna on chain0 doesn't change the alt_rssi value for us. We 
only noticed that frames with alt_rssi != -128 have  the value rx_ant_conf == 
1 (LNA2) when only chain1 is attached and rx_ant_conf == 2 (LNA1) when 
both/chain0-only are attached. Still most of the packets had alt_rssi == -128 
and we saw changes in curr_main_set and curr_alt_set (after lot of data was 
sent).

> also please see the throughput difference with/without antenna
> diversity with one antenna broken.

We (Simon and me) tried to play with the antennas and came to following 
results:

* Both attached: 45 Mibit/s
* chain0 attached: 45 Mibit/s
* chain1 attached: 15 seconds nearly nothing, after that 25 Mibit/s

> I will check out the proper technical reason for such a
> preference/compare with AR9285 (or) if its a bug in the code itself.
> thanks for looking into this feature!

Thanks

Kind regards,
	Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120706/fbaea517/attachment.pgp 

WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
	ath9k-devel@lists.ath9k.org,
	Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>,
	Adrian Chadd <adrian@freebsd.org>,
	Marek Lindner <lindner_marek@yahoo.de>,
	linux-wireless@vger.kernel.org, Gabor Juhos <juhosg@openwrt.org>
Subject: Re: ath9k: Problems with diversity on AR9330
Date: Fri, 06 Jul 2012 17:13:42 +0200	[thread overview]
Message-ID: <5244861.J1Tyef1FCX@bentobox> (raw)
In-Reply-To: <CAD2nsn1=PDBTRXumDh93DzvmFcBnyFeLD-5c5oSJmv3OO6LWGw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]

On Friday 06 July 2012 19:32:41 Mohammed Shafi wrote:
> Hi Simon,
> 
> On Fri, Jul 6, 2012 at 6:20 PM, Simon Wunderlich
> 
> <simon.wunderlich@s2003.tu-chemnitz.de> wrote:
> > Hey,
> > 
> > we have trouble with an AR9330 (Hornet) based AP. This device has 2
> > antennas, and is supposed to support diversity (2 RX, 1 TX). However,
> > diversity is not really enabled because the "alternative" antenna is not
> > considered as "good", because not enough frames are received. It seems
> > that at 99% of the time, alt_rssi (read from rs->rs_rssi_ctl1) is invalid
> > (set to ATH9K_RSSI_BAD, -128), while main_rssi (read from
> > rs->rs_rssi_ctl0) usually has sane values.
> its been some good amount of time i had taken/tested take a look at
> this. actually Gabor Juhos added the support for AR9330.
> seems AR9003 family chipsets can exhibit this behaviour. i quickly
> checked with AR9285(AR9002) which seems to have a positive RSSI
> regulary in ctl0/ctl1.
> i also have a AR9485(AR9003 family) which might be similar to AR9330.
> just checked with removing the antenna in chain0 seems to bring
> positive values in rssi_ctl1.
> I just also observer the chain0 is "preferred" unless the RSSI is so
> poor in it so chain1 is taken.
> Please check if this work out for your case too.

Removing the antenna on chain0 doesn't change the alt_rssi value for us. We 
only noticed that frames with alt_rssi != -128 have  the value rx_ant_conf == 
1 (LNA2) when only chain1 is attached and rx_ant_conf == 2 (LNA1) when 
both/chain0-only are attached. Still most of the packets had alt_rssi == -128 
and we saw changes in curr_main_set and curr_alt_set (after lot of data was 
sent).

> also please see the throughput difference with/without antenna
> diversity with one antenna broken.

We (Simon and me) tried to play with the antennas and came to following 
results:

* Both attached: 45 Mibit/s
* chain0 attached: 45 Mibit/s
* chain1 attached: 15 seconds nearly nothing, after that 25 Mibit/s

> I will check out the proper technical reason for such a
> preference/compare with AR9285 (or) if its a bug in the code itself.
> thanks for looking into this feature!

Thanks

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-06 15:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 12:50 [ath9k-devel] ath9k: Problems with diversity on AR9330 Simon Wunderlich
2012-07-06 12:50 ` Simon Wunderlich
2012-07-06 14:02 ` [ath9k-devel] " Mohammed Shafi
2012-07-06 14:02   ` Mohammed Shafi
2012-07-06 15:13   ` Sven Eckelmann [this message]
2012-07-06 15:13     ` Sven Eckelmann
2012-07-06 16:35     ` [ath9k-devel] " Sven Eckelmann
2012-07-06 16:35       ` Sven Eckelmann
2012-07-07  9:58       ` [ath9k-devel] " Mohammed Shafi
2012-07-07  9:58         ` Mohammed Shafi
2012-07-07 10:14         ` [ath9k-devel] " Mohammed Shafi
2012-07-07 10:14           ` Mohammed Shafi
2012-07-07 10:31           ` [ath9k-devel] " Sunil Mehta
2012-07-07 10:31             ` Sunil Mehta
2012-07-07 10:36             ` Mohammed Shafi
2012-07-07 10:36               ` Mohammed Shafi
2012-07-07 11:33               ` Sunil Mehta
2012-07-07 11:33                 ` Sunil Mehta
2012-07-07 10:32           ` Mohammed Shafi
2012-07-07 10:32             ` Mohammed Shafi
2012-07-07 18:59             ` [ath9k-devel] " Simon Wunderlich
2012-07-07 18:59               ` Simon Wunderlich
2012-07-09 14:03               ` [ath9k-devel] " Mohammed Shafi
2012-07-09 14:03                 ` Mohammed Shafi
2012-07-19  5:08                 ` [ath9k-devel] " Mohammed Shafi
2012-07-19  5:08                   ` 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=5244861.J1Tyef1FCX@bentobox \
    --to=sven@narfation.org \
    --cc=ath9k-devel@lists.ath9k.org \
    /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.