From: Sunil Mehta <sunil2@telenetsystems.com>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>,
<linux-wireless@vger.kernel.org>, <ath9k-devel@lists.ath9k.org>
Subject: Re: [ath9k-devel] ath9k: Problems with diversity on AR9330
Date: Sat, 07 Jul 2012 16:01:56 +0530 [thread overview]
Message-ID: <CC1E0C97.12FC3%sunil2@telenetsystems.com> (raw)
In-Reply-To: <CAD2nsn1-ZrKQxTYc_YZ6ETxovD9o7=Ygd2j2MxJiq8Vsiu19QQ@mail.gmail.com>
Hi Shafi,
We are facing similar problems with configuring the LNA2 of AR9331 for
diversity. Even though we try to set the RXCHAINMASK = 0x03, on checking
the value, it keeps showing as 0x01.
We are currently using LSDK-9.2.0_U10.1020. It appears that some where the
value may be hardcoded to 0x01 in this Release.
Can you suggest how to solve this.
Regards,
Sunil.
On 7/7/12 3:44 PM, "Mohammed Shafi" <shafi.wireless@gmail.com> wrote:
>On Sat, Jul 7, 2012 at 3:28 PM, Mohammed Shafi <shafi.wireless@gmail.com>
>wrote:
>> Hi Sven,
>>
>> On Fri, Jul 6, 2012 at 10:05 PM, Sven Eckelmann <sven@narfation.org>
>>wrote:
>>> 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.
>>
>> thanks, i saw the logs. i could do some analysis with AR9485/AR9285.
>> as you had said before
>> alt_rssi is -128 when one antenna is unplugged, while having both out
>> seems to bring some
>> +tive value for alt_rssi.
>>
>>>
>>> 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.
>>
>> thanks i would check this out. As the algorithm itself is bit
>> complex, i would just revisit
>> and check it out. If i remember correctly Fast antenna diversity was
>> working fine with AR9485.
>
>further i check with the CCK/DETECT and MC_GAIN_CTRL in ar9485, it seems
>to be
> ar9003_hw_ant_ctrl_apply CCK_DETECT 80be6788
> ar9003_hw_ant_ctrl_apply MC_GAIN_CTRLL 13ef0200
>will check it out whats the one bit difference in CCK_DETECT
>
>
>>
>>>
>>> Kind regards
>>> Sven
>>
>>
>>
>> --
>> thanks,
>> shafi
>
>
>
>--
>thanks,
>shafi
>_______________________________________________
>ath9k-devel mailing list
>ath9k-devel@lists.ath9k.org
>https://lists.ath9k.org/mailman/listinfo/ath9k-devel
next prev parent reply other threads:[~2012-07-07 10:38 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
2012-07-07 9:58 ` Mohammed Shafi
2012-07-07 10:14 ` Mohammed Shafi
2012-07-07 10:31 ` Sunil Mehta [this message]
2012-07-07 10:36 ` [ath9k-devel] " 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=CC1E0C97.12FC3%sunil2@telenetsystems.com \
--to=sunil2@telenetsystems.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed@qca.qualcomm.com \
--cc=shafi.wireless@gmail.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).