[ath9k-devel] AR9287 ; 2-wire coexistence expected behavior

[sandeep suresh <sandeep.suresh@yahoo.co.in>]

Hello Mr.Adrian,
????Thanks for your observation. I changed the weight register to reflect the weightage of BT (= 0xFFFF) and WLAN(= 0x0000) ?which was verified after dumping the registers. I will try changing the mode and inform the results. What exactly is the meaning of these modes:
a) Legacy rx_clear mode
b) Untimed/unslotted mode
c) Slotted mode?
?
Thanks & regards
Sandeep Suresh.


________________________________
From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: Sujith Manoharan <sujith@msujith.org>; ath9k-devel <ath9k-devel@lists.ath9k.org>; "linux-wireless at vger.kernel.org" <linux-wireless@vger.kernel.org> 
Sent: Tuesday, 16 April 2013 10:30 PM
Subject: Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior


On 15 April 2013 20:55, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello Mr.Adrian,
>? ? Got the debugfs working. I used the regdump under
> "/sys/kernel/debug/ieee80211/phy0/ath9k". The following are the values:
> ar5416phy.h:#define? ? AR_BT_COEX_MODE? ? ? ? ? ? 0x8170? ? ? ? Value is:
> 0x050a5b00

How's that being set? it looks like you're enabling mode 2 (slotted)
versus 2-wire or 3-wire.

Look at the code and HAL definitions. You want 2-wire / legacy
rx_clear mode for the _MODE_ field inside AR_BT_COEX_MODE.


> ar5416phy.h:#define? ? AR_BT_COEX_WEIGHT? ? ? ? ? 0x8174? ? ? Value is:
> 0xa8a8ff55

Double-check your weight values and make sure that they're actually
-correct- for having BT stomp wifi in all instances.



Adrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130417/1a22c804/attachment.htm