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

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

Hello Mr.Adrian,
????Thanks for your comments. 
?
In fact I have used the same ath9k code available and called the initialization for 2-wire coexistence that was missing. I will test further (the following aspects)and commit the code with some documentation so that it will be useful for the community.
?
Can you please further help me:
1. Commands to enable hostapd logging whichwill log the MLME events.
2. How can I enable missed beacon transmit events? Does it get automatically enabled during "modprobe ath9k diag=0xFFFFFFFF" ?

?
Thanks & regards
Sandeep Suresh

________________________________
From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: ath9k-devel <ath9k-devel@lists.ath9k.org>; "linux-wireless at vger.kernel.org" <linux-wireless@vger.kernel.org> 
Sent: Tuesday, 21 May 2013 8:03 PM
Subject: Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior


Hi!

On 20 May 2013 23:40, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello Mr.Adrian,
>? ? Greetings! I resumed my experiments with 2-wire co-existence with AR9287
> in WiFi AP mode.
> I was able to see that WLAN_STATUS signal being suppressed when BT_ACTIVE is
> enabled. I used a 100ms On and 100ms Off (Period = 200ms; 50% dc) for
> BT_ACTIVE. Just want to confirm the following before ensuring that I am
> seeing the expected behavior:
>
Cool! Can you share some code and register settings to enable this?

> 1. As I am running the WiFi AP with co-existence, other WiFi clients are
> connected to my AP. by means of diagnsosis (I have enabled diagnosis with
> modprobe ath9k btcoex_enabled=1 diag=0xffffffff), how can I find out if any
> WiFi clients are loosing connection and re-connecting back to AP.

I think you should enable hostapd logging. That will log the MLME events.

> 2. How can I come to know if any of the beacons in WiFi AP mode are getting
> missed? Diagnosis messages that I can look at.

You can look for missed beacon transmit events. That should tell you
if you're missing beacon transmission at all.

> 3. As diagnosis is enabled I see the following....is this a concern as there
> is disable and enable of IER?
> <7>ath: disable IER
> <7>ath: AR_IMR 0x918104b0 IER 0x1
> <7>ath: tx queue 2 (4bfc09c4), link ffde09c4
> <7>ath: enable IER
> <7>ath: Enable TXE on queue: 2
> <7>ath: disable IER
> <7>ath: AR_IMR 0x918104b0 IER 0x1

That's fine. That's what ath9k does with interrupts. :-)

> 4. How can I come to know if the ath9k drivers are getting reset and
> reinitializing?

There's a hw reset routine that gets called. You can just look for the
logging from that, or add a printk() yourself.



Adrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130522/8357d8b0/attachment.htm