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 18:35:55 +0200 [thread overview]
Message-ID: <4991617.K7XqcvhjBY@bentobox> (raw)
In-Reply-To: <5244861.J1Tyef1FCX@bentobox>
[-- Attachment #1.1: Type: text/plain, Size: 1163 bytes --]
On Friday 06 July 2012 17:13:42 Sven Eckelmann wrote:
[...]
> > 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).
Here are some logs. We added some debug printk before first check in
ath_ant_comb_scan ("if (main_rssi > 0 && alt_rssi > 0) {"). We can see a
difference in the output after (a more or less long time) both antennas were
unplugged. The output looks extreme different when at least one antenna is
attached.
alt_ant_conf is calculated using
"alt_ant_conf = (rs->rs_rssi_ctl[2]) & ATH_ANT_RX_MASK;" and could be wrong.
curr_alt_set and curr_main_set come from div_ant_conf queried using
ath9k_hw_antdiv_comb_conf_get.
Kind regards
Sven
[-- Attachment #1.2: after_both_antennas_unplugged.txt.zip --]
[-- Type: application/zip, Size: 1355 bytes --]
[-- Attachment #1.3: at_least_one_antenna.txt.zip --]
[-- Type: application/zip, Size: 1297 bytes --]
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-06 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 12:50 ath9k: Problems with diversity on AR9330 Simon Wunderlich
2012-07-06 14:02 ` Mohammed Shafi
2012-07-06 15:13 ` Sven Eckelmann
2012-07-06 16:35 ` Sven Eckelmann [this message]
2012-07-07 9:58 ` Mohammed Shafi
2012-07-07 10:14 ` Mohammed Shafi
2012-07-07 10:31 ` [ath9k-devel] " Sunil Mehta
2012-07-07 10:36 ` Mohammed Shafi
2012-07-07 11:33 ` Sunil Mehta
2012-07-07 10:32 ` Mohammed Shafi
2012-07-07 18:59 ` Simon Wunderlich
2012-07-09 14:03 ` 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=4991617.K7XqcvhjBY@bentobox \
--to=sven@narfation.org \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=juhosg@openwrt.org \
--cc=lindner_marek@yahoo.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed@qca.qualcomm.com \
--cc=shafi.wireless@gmail.com \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
/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).