[ath9k-devel] WLAN and BT Co-existence for AR9287 and AR3011

[ath9k-devel] WLAN and BT Co-existence for AR9287 and AR3011

[sandeep suresh]

Dear Experts,
????This is regarding the WiFi (Wireless LAN) and Bluetooth co-existence for AR9287 and AR3011. As I understand from the website there is a co-existence solution for AR9285 and AR3011. Can you please help me with:
1. Drivers? (btcoex.c etc) for the WLAN and BT co-existence for linux system for AR9287 and AR3011? Please send me the link so that I can download the same. 
?
2. Appreciate if anyone can share the usage of the APIsfor Btcoex.c ?in a typical application.
?
3. The other basic question I had was, is it possible say every 500ms, I can allocate the media for WLAN for 300ms and for BT for 200ms? How can we do this?
?
Thanks for your time and response.
Kind regards
Sandeep Suresh.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130206/13b65902/attachment.htm 

[ath9k-devel] WLAN and BT Co-existence for AR9287 and AR3011

[sandeep suresh]

Good morning dear experts,
????????????? As I am new to the group , need your help in addressing the following questions, Please.
Please help on this:
1. Drivers? (btcoex.c etc) for the WLAN and BT co-existence for linux system for AR9287 and AR3011? Please send me the link so that I can download the same. 
?
2. Appreciate if anyone can share the usage of the APIsfor Btcoex.c ?in a typical application.
?
3. The other basic question I had was, is it possible say every 500ms, I can allocate the media for WLAN for 300ms and for BT for 200ms? How can we do this?
?
Thanks for your time and response.
Kind regards
Sandeep Suresh.


________________________________
From: sandeep suresh <sandeep.suresh@yahoo.co.in>
To: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org> 
Sent: Wednesday, 6 February 2013 4:25 PM
Subject: [ath9k-devel] WLAN and BT Co-existence for AR9287 and AR3011


Dear Experts,
????This is regarding the WiFi (Wireless LAN) and Bluetooth co-existence for AR9287 and AR3011. As I understand from the website there is a co-existence solution for AR9285 and AR3011. Can you please help me with:
1. Drivers? (btcoex.c etc) for the WLAN and BT co-existence for linux system for AR9287 and AR3011? Please send me the link so that I can download the same. 
?
2. Appreciate if anyone can share the usage of the APIsfor Btcoex.c ?in a typical application.
?
3. The other basic question I had was, is it possible say every 500ms, I can allocate the media for WLAN for 300ms and for BT for 200ms? How can we do this?
?
Thanks for your time and response.
Kind regards
Sandeep Suresh.
?
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130210/dc4225fd/attachment.htm 

[ath9k-devel] Please help; WLAN and BT Co-existence

[sandeep suresh]

Good morning dear experts,
????????????? As I am new to the group , need your help in addressing the following questions, Please.
Please help on this:
1. The?basic question I had was, is it possible say every 500ms, I can allocate the media for WLAN for 300ms and for BT for 200ms? How can we do this?
?
Thanks for your time and response.
Kind regards
Sandeep Suresh.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130222/446f8759/attachment.htm 

[ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe pins

[sandeep suresh]

Dear experts,
????AR9287 is used inside the WLE200N2 PCIe mini card module from Compex. There are 76 pins on AR9287 whereas the WLE200N2 PCIe interface has 52 pins. Can anyone help me with the mapping between AR9287 to WLE200N2? Is the mapping fixed by hardware design or can be changed in software by configuration? Are there register settings or how is it taken care in ath9k? Please help.
?
Thanks & regards
Sandeep.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130319/70c55125/attachment-0001.htm 

[ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe pins

[Peter Stuge]

sandeep suresh wrote:
> There are 76 pins on AR9287 whereas the WLE200N2 PCIe interface has 52 pins.
> Can anyone help me with the mapping between AR9287 to WLE200N2?

Yes, Compex.


> Is the mapping fixed by hardware design or can be changed in software

Why do you care?


//Peter

[ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe pins

[sandeep suresh]

Thanks Peter.
Currently on our board only certain pins from PCIe are brought out. If the mapping can be changed in software, than I can map to these already brought out pins.
Regards
Sandeep.


________________________________
From: Peter Stuge <peter@stuge.se>
To: ath9k-devel at lists.ath9k.org 
Sent: Tuesday, 19 March 2013 8:00 AM
Subject: Re: [ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe pins

sandeep suresh wrote:
> There are 76 pins on AR9287 whereas the WLE200N2 PCIe interface has 52 pins.
> Can anyone help me with the mapping between AR9287 to WLE200N2?

Yes, Compex.


> Is the mapping fixed by hardware design or can be changed in software

Why do you care?


//Peter
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130319/6f1b43cd/attachment.htm 

[ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe pins

[Adrian Chadd]

No, it's not under software control.



adrian

On 19 March 2013 04:47, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Thanks Peter.
> Currently on our board only certain pins from PCIe are brought out. If the
> mapping can be changed in software, than I can map to these already brought
> out pins.
> Regards
> Sandeep.
>
> From: Peter Stuge <peter@stuge.se>
> To: ath9k-devel at lists.ath9k.org
> Sent: Tuesday, 19 March 2013 8:00 AM
> Subject: Re: [ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe
> pins
>
> sandeep suresh wrote:
>> There are 76 pins on AR9287 whereas the WLE200N2 PCIe interface has 52
>> pins.
>> Can anyone help me with the mapping between AR9287 to WLE200N2?
>
> Yes, Compex.
>
>
>> Is the mapping fixed by hardware design or can be changed in software
>
> Why do you care?
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe pins

[Peter Stuge]

sandeep suresh wrote:
> Currently on our board only certain pins from PCIe are brought out.

You can't magically turn a USB-only miniPCIe-slot into one with both
PCIe and USB. You'll need either another mainboard or a USB-based
miniPCIe card.


//Peter

[ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe pins

[sandeep suresh]

Thanks Adrian and Peter for your comments. We are in touch with COPEX and will get the necessary changes done.



________________________________
From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: Peter Stuge <peter@stuge.se>; "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org> 
Sent: Tuesday, 19 March 2013 7:06 PM
Subject: Re: [ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe pins

No, it's not under software control.



adrian

On 19 March 2013 04:47, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Thanks Peter.
> Currently on our board only certain pins from PCIe are brought out. If the
> mapping can be changed in software, than I can map to these already brought
> out pins.
> Regards
> Sandeep.
>
> From: Peter Stuge <peter@stuge.se>
> To: ath9k-devel at lists.ath9k.org
> Sent: Tuesday, 19 March 2013 8:00 AM
> Subject: Re: [ath9k-devel] Mapping between AR9287 pins to WLE200N2 PCIEe
> pins
>
> sandeep suresh wrote:
>> There are 76 pins on AR9287 whereas the WLE200N2 PCIe interface has 52
>> pins.
>> Can anyone help me with the mapping between AR9287 to WLE200N2?
>
> Yes, Compex.
>
>
>> Is the mapping fixed by hardware design or can be changed in software
>
> Why do you care?
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130320/30b36b17/attachment.htm 

[ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

[sandeep suresh]

Good morning Dear Experts,
????This is a query regarding WiFi Bluetooth co-existence for AR9287. From the datasheet I understand that it supports 2-wire/3-wire co-existence. But does AR9287 supports WiFi and BT co-existence in:
(a) WiFi in Access Point Mode.
(b) WiFi in Client Mode.
(c) WiFi in Hybrid Mode (combination of AP and Client mode).
Please clarify.
Thanks & regards
Sandeep
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130320/1244d437/attachment-0001.htm 

[ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

[Adrian Chadd]

Hi,

The bluetooth coexistence in ath9k implements a static btcoex method.
You can tweak the various BT weights based on BT and wifi traffic
patterns in order to implement whatever you wish.



Adrian

On 19 March 2013 20:00, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Good morning Dear Experts,
>     This is a query regarding WiFi Bluetooth co-existence for AR9287. From
> the datasheet I understand that it supports 2-wire/3-wire co-existence. But
> does AR9287 supports WiFi and BT co-existence in:
> (a) WiFi in Access Point Mode.
> (b) WiFi in Client Mode.
> (c) WiFi in Hybrid Mode (combination of AP and Client mode).
> Please clarify.
> Thanks & regards
> Sandeep
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

[sandeep suresh]

Hello Mr.Adrian & other experts,
????Thanks for the quick response.
?
1. So, does it mean that coexistence (BTCOEX) is independent of the WiFi operating modes like Access Point, client and Hybrid?
?2. Also, I wanted to understand if anyone has ath9k with AR9287 with BTCOEX enabled has been tested in WiFi AP mode? Sorry if this is a basic question. Because I am with the information that when WiFi is not active during BTCOEX mode, it has to be?put in?sleep. And Sleep mode cannot be handled with WiFi chipset configured?as Access Point.
?
3. Is there any documentation on some guidelines, application notes for tweaking the weights for operation on 2-wire/3-wire? If there are some examples it will be helpful. Because could not find any details/documentation on this topic :-(.
?
4. In ath9k, how can we configure 2-wire or 3-wire for AR9287?
?
Thanks & regards
Sandeep.


________________________________
From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org> 
Sent: Wednesday, 20 March 2013 9:30 AM
Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

Hi,

The bluetooth coexistence in ath9k implements a static btcoex method.
You can tweak the various BT weights based on BT and wifi traffic
patterns in order to implement whatever you wish.



Adrian

On 19 March 2013 20:00, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Good morning Dear Experts,
>? ? This is a query regarding WiFi Bluetooth co-existence for AR9287. From
> the datasheet I understand that it supports 2-wire/3-wire co-existence. But
> does AR9287 supports WiFi and BT co-existence in:
> (a) WiFi in Access Point Mode.
> (b) WiFi in Client Mode.
> (c) WiFi in Hybrid Mode (combination of AP and Client mode).
> Please clarify.
> Thanks & regards
> Sandeep
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130320/9051ecab/attachment.htm 

[ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

[Mohammed Shafi]

On Wed, Mar 20, 2013 at 11:33 AM, sandeep suresh
<sandeep.suresh@yahoo.co.in> wrote:
> Hello Mr.Adrian & other experts,
>     Thanks for the quick response.
>
> 1. So, does it mean that coexistence (BTCOEX) is independent of the WiFi
> operating modes like Access Point, client and Hybrid?

nope BTCOEX is to have BT operating while WLAN is running.

>
> 2. Also, I wanted to understand if anyone has ath9k with AR9287 with BTCOEX
> enabled has been tested in WiFi AP mode? Sorry if this is a basic question.
> Because I am with the information that when WiFi is not active during BTCOEX
> mode, it has to be put in sleep. And Sleep mode cannot be handled with WiFi
> chipset configured as Access Point.

STA mode tested, not sure about AP mode

>
> 3. Is there any documentation on some guidelines, application notes for
> tweaking the weights for operation on 2-wire/3-wire? If there are some
> examples it will be helpful. Because could not find any
> details/documentation on this topic :-(.

http://linuxwireless.org/en/users/Drivers/ath9k/btcoex

>
> 4. In ath9k, how can we configure 2-wire or 3-wire for AR9287?
>
> Thanks & regards
> Sandeep.
>
> From: Adrian Chadd <adrian@freebsd.org>
> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Sent: Wednesday, 20 March 2013 9:30 AM
> Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client
> and Hybrid Mode
>
> Hi,
>
> The bluetooth coexistence in ath9k implements a static btcoex method.
> You can tweak the various BT weights based on BT and wifi traffic
> patterns in order to implement whatever you wish.
>
>
>
> Adrian
>
> On 19 March 2013 20:00, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>> Good morning Dear Experts,
>>    This is a query regarding WiFi Bluetooth co-existence for AR9287. From
>> the datasheet I understand that it supports 2-wire/3-wire co-existence.
>> But
>> does AR9287 supports WiFi and BT co-existence in:
>> (a) WiFi in Access Point Mode.
>> (b) WiFi in Client Mode.
>> (c) WiFi in Hybrid Mode (combination of AP and Client mode).
>> Please clarify.
>> Thanks & regards
>> Sandeep
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>



-- 
thanks,
shafi

[ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

[Adrian Chadd]

Hi,

The wlan chip isn't put to sleep when btcoex is running; it's just
told to not transmit.

There's not really anything public about how this stuff works. I'm
trying to get this stuff open but it takes time.




Adrian


On 19 March 2013 23:03, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello Mr.Adrian & other experts,
>     Thanks for the quick response.
>
> 1. So, does it mean that coexistence (BTCOEX) is independent of the WiFi
> operating modes like Access Point, client and Hybrid?
>
> 2. Also, I wanted to understand if anyone has ath9k with AR9287 with BTCOEX
> enabled has been tested in WiFi AP mode? Sorry if this is a basic question.
> Because I am with the information that when WiFi is not active during BTCOEX
> mode, it has to be put in sleep. And Sleep mode cannot be handled with WiFi
> chipset configured as Access Point.
>
> 3. Is there any documentation on some guidelines, application notes for
> tweaking the weights for operation on 2-wire/3-wire? If there are some
> examples it will be helpful. Because could not find any
> details/documentation on this topic :-(.
>
> 4. In ath9k, how can we configure 2-wire or 3-wire for AR9287?
>
> Thanks & regards
> Sandeep.
>
> From: Adrian Chadd <adrian@freebsd.org>
> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Sent: Wednesday, 20 March 2013 9:30 AM
> Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client
> and Hybrid Mode
>
> Hi,
>
> The bluetooth coexistence in ath9k implements a static btcoex method.
> You can tweak the various BT weights based on BT and wifi traffic
> patterns in order to implement whatever you wish.
>
>
>
> Adrian
>
> On 19 March 2013 20:00, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>> Good morning Dear Experts,
>>    This is a query regarding WiFi Bluetooth co-existence for AR9287. From
>> the datasheet I understand that it supports 2-wire/3-wire co-existence.
>> But
>> does AR9287 supports WiFi and BT co-existence in:
>> (a) WiFi in Access Point Mode.
>> (b) WiFi in Client Mode.
>> (c) WiFi in Hybrid Mode (combination of AP and Client mode).
>> Please clarify.
>> Thanks & regards
>> Sandeep
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>

[ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

[sandeep suresh]

Hello Mr.Adrian, Mr.Mohammed & others,
????Thanks for your quick responses. Did not understand the first response.
Does BTCOEX mode works in WiFi configured in AP mode, Client mode and Hybrid mode, Please?
Thanks & regards
Sandeep


________________________________
From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org> 
Sent: Thursday, 21 March 2013 12:23 AM
Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

Hi,

The wlan chip isn't put to sleep when btcoex is running; it's just
told to not transmit.

There's not really anything public about how this stuff works. I'm
trying to get this stuff open but it takes time.




Adrian


On 19 March 2013 23:03, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello Mr.Adrian & other experts,
>? ? Thanks for the quick response.
>
> 1. So, does it mean that coexistence (BTCOEX) is independent of the WiFi
> operating modes like Access Point, client and Hybrid?
>
> 2. Also, I wanted to understand if anyone has ath9k with AR9287 with BTCOEX
> enabled has been tested in WiFi AP mode? Sorry if this is a basic question.
> Because I am with the information that when WiFi is not active during BTCOEX
> mode, it has to be put in sleep. And Sleep mode cannot be handled with WiFi
> chipset configured as Access Point.
>
> 3. Is there any documentation on some guidelines, application notes for
> tweaking the weights for operation on 2-wire/3-wire? If there are some
> examples it will be helpful. Because could not find any
> details/documentation on this topic :-(.
>
> 4. In ath9k, how can we configure 2-wire or 3-wire for AR9287?
>
> Thanks & regards
> Sandeep.
>
> From: Adrian Chadd <adrian@freebsd.org>
> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Sent: Wednesday, 20 March 2013 9:30 AM
> Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client
> and Hybrid Mode
>
> Hi,
>
> The bluetooth coexistence in ath9k implements a static btcoex method.
> You can tweak the various BT weights based on BT and wifi traffic
> patterns in order to implement whatever you wish.
>
>
>
> Adrian
>
> On 19 March 2013 20:00, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>> Good morning Dear Experts,
>>? ? This is a query regarding WiFi Bluetooth co-existence for AR9287. From
>> the datasheet I understand that it supports 2-wire/3-wire co-existence.
>> But
>> does AR9287 supports WiFi and BT co-existence in:
>> (a) WiFi in Access Point Mode.
>> (b) WiFi in Client Mode.
>> (c) WiFi in Hybrid Mode (combination of AP and Client mode).
>> Please clarify.
>> Thanks & regards
>> Sandeep
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130321/fe8643f7/attachment.htm 

[ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

[Adrian Chadd]

btcoex mode is just a way to prioritise whether BT or WLAN operation
is occuring.

It's right now "static" in ath9k. The dynamic bluetooth parameter
tweaking in the MAC isn't being done.

So it's not "works" or "not works." It's "who knows." There's no
reason it won't work. Someone just needs to write some userland facing
APIs to get control of the btcoex parameters and start experimenting.



adrian


On 20 March 2013 19:40, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello Mr.Adrian, Mr.Mohammed & others,
>     Thanks for your quick responses. Did not understand the first response.
> Does BTCOEX mode works in WiFi configured in AP mode, Client mode and Hybrid
> mode, Please?
> Thanks & regards
> Sandeep
> From: Adrian Chadd <adrian@freebsd.org>
> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Sent: Thursday, 21 March 2013 12:23 AM
>
> Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client
> and Hybrid Mode
>
> Hi,
>
> The wlan chip isn't put to sleep when btcoex is running; it's just
> told to not transmit.
>
> There's not really anything public about how this stuff works. I'm
> trying to get this stuff open but it takes time.
>
>
>
>
> Adrian
>
>
> On 19 March 2013 23:03, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>> Hello Mr.Adrian & other experts,
>>    Thanks for the quick response.
>>
>> 1. So, does it mean that coexistence (BTCOEX) is independent of the WiFi
>> operating modes like Access Point, client and Hybrid?
>>
>> 2. Also, I wanted to understand if anyone has ath9k with AR9287 with
>> BTCOEX
>> enabled has been tested in WiFi AP mode? Sorry if this is a basic
>> question.
>> Because I am with the information that when WiFi is not active during
>> BTCOEX
>> mode, it has to be put in sleep. And Sleep mode cannot be handled with
>> WiFi
>> chipset configured as Access Point.
>>
>> 3. Is there any documentation on some guidelines, application notes for
>> tweaking the weights for operation on 2-wire/3-wire? If there are some
>> examples it will be helpful. Because could not find any
>> details/documentation on this topic :-(.
>>
>> 4. In ath9k, how can we configure 2-wire or 3-wire for AR9287?
>>
>> Thanks & regards
>> Sandeep.
>>
>> From: Adrian Chadd <adrian@freebsd.org>
>> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
>> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
>> Sent: Wednesday, 20 March 2013 9:30 AM
>> Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP,
>> Client
>> and Hybrid Mode
>>
>> Hi,
>>
>> The bluetooth coexistence in ath9k implements a static btcoex method.
>> You can tweak the various BT weights based on BT and wifi traffic
>> patterns in order to implement whatever you wish.
>>
>>
>>
>> Adrian
>>
>> On 19 March 2013 20:00, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>>> Good morning Dear Experts,
>>>    This is a query regarding WiFi Bluetooth co-existence for AR9287. From
>>> the datasheet I understand that it supports 2-wire/3-wire co-existence.
>>> But
>>> does AR9287 supports WiFi and BT co-existence in:
>>> (a) WiFi in Access Point Mode.
>>> (b) WiFi in Client Mode.
>>> (c) WiFi in Hybrid Mode (combination of AP and Client mode).
>>> Please clarify.
>>> Thanks & regards
>>> Sandeep
>>>
>>> _______________________________________________
>>> ath9k-devel mailing list
>>> ath9k-devel at lists.ath9k.org
>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>>
>>
>>
>
>

[ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

[sandeep suresh]

Thanks Mr. Adrian for your response.



________________________________
From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org> 
Sent: Thursday, 21 March 2013 9:32 AM
Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client and Hybrid Mode

btcoex mode is just a way to prioritise whether BT or WLAN operation
is occuring.

It's right now "static" in ath9k. The dynamic bluetooth parameter
tweaking in the MAC isn't being done.

So it's not "works" or "not works." It's "who knows." There's no
reason it won't work. Someone just needs to write some userland facing
APIs to get control of the btcoex parameters and start experimenting.



adrian


On 20 March 2013 19:40, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello Mr.Adrian, Mr.Mohammed & others,
>? ? Thanks for your quick responses. Did not understand the first response.
> Does BTCOEX mode works in WiFi configured in AP mode, Client mode and Hybrid
> mode, Please?
> Thanks & regards
> Sandeep
> From: Adrian Chadd <adrian@freebsd.org>
> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Sent: Thursday, 21 March 2013 12:23 AM
>
> Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP, Client
> and Hybrid Mode
>
> Hi,
>
> The wlan chip isn't put to sleep when btcoex is running; it's just
> told to not transmit.
>
> There's not really anything public about how this stuff works. I'm
> trying to get this stuff open but it takes time.
>
>
>
>
> Adrian
>
>
> On 19 March 2013 23:03, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>> Hello Mr.Adrian & other experts,
>>? ? Thanks for the quick response.
>>
>> 1. So, does it mean that coexistence (BTCOEX) is independent of the WiFi
>> operating modes like Access Point, client and Hybrid?
>>
>> 2. Also, I wanted to understand if anyone has ath9k with AR9287 with
>> BTCOEX
>> enabled has been tested in WiFi AP mode? Sorry if this is a basic
>> question.
>> Because I am with the information that when WiFi is not active during
>> BTCOEX
>> mode, it has to be put in sleep. And Sleep mode cannot be handled with
>> WiFi
>> chipset configured as Access Point.
>>
>> 3. Is there any documentation on some guidelines, application notes for
>> tweaking the weights for operation on 2-wire/3-wire? If there are some
>> examples it will be helpful. Because could not find any
>> details/documentation on this topic :-(.
>>
>> 4. In ath9k, how can we configure 2-wire or 3-wire for AR9287?
>>
>> Thanks & regards
>> Sandeep.
>>
>> From: Adrian Chadd <adrian@freebsd.org>
>> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
>> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
>> Sent: Wednesday, 20 March 2013 9:30 AM
>> Subject: Re: [ath9k-devel] AR9287; BT Coexistence working in WiFi AP,
>> Client
>> and Hybrid Mode
>>
>> Hi,
>>
>> The bluetooth coexistence in ath9k implements a static btcoex method.
>> You can tweak the various BT weights based on BT and wifi traffic
>> patterns in order to implement whatever you wish.
>>
>>
>>
>> Adrian
>>
>> On 19 March 2013 20:00, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>>> Good morning Dear Experts,
>>>? ? This is a query regarding WiFi Bluetooth co-existence for AR9287. From
>>> the datasheet I understand that it supports 2-wire/3-wire co-existence.
>>> But
>>> does AR9287 supports WiFi and BT co-existence in:
>>> (a) WiFi in Access Point Mode.
>>> (b) WiFi in Client Mode.
>>> (c) WiFi in Hybrid Mode (combination of AP and Client mode).
>>> Please clarify.
>>> Thanks & regards
>>> Sandeep
>>>
>>> _______________________________________________
>>> ath9k-devel mailing list
>>> ath9k-devel at lists.ath9k.org
>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130321/b9e65795/attachment.htm 

[ath9k-devel] AR9287; BT Coexistence with 3-wire

[sandeep suresh]

Hello All,
????In ath9k, only BT co-existence for 2-wire interface is selected for AR9287. Please refer to the code section below in btcoex.c. Does that mean?the 3-wire interface based drivers available for AR9285 and AR9300+ cannot be used for AR9287?
?
if (AR_SREV_9300_20_OR_LATER(ah)) {
??btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
??btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9300;
??btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9300;
??btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9300;
?} else if (AR_SREV_9280_20_OR_LATER(ah)) {
??btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9280;
??btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9280;
??if (AR_SREV_9285(ah)) {
???btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
???btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9285;
??} else {
???btcoex_hw->scheme = ATH_BTCOEX_CFG_2WIRE;
??}
?
Regards
Sandeep
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130321/3f584237/attachment.htm 

[ath9k-devel] AR9287; BT Coexistence with 3-wire

[Adrian Chadd]

I'll have to check this tomorrow.

It depends on what kind of BT chip was put on the AR9287 combo board
that you have. And I don't know whether it uses 2 wire or 3 wire.

There's a whole bunch of functions in the reference driver HAL which
tune the BT coexistence parameters. I'll see if I can dig that up too.



Adrian

On 20 March 2013 22:07, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello All,
>     In ath9k, only BT co-existence for 2-wire interface is selected for
> AR9287. Please refer to the code section below in btcoex.c. Does that mean
> the 3-wire interface based drivers available for AR9285 and AR9300+ cannot
> be used for AR9287?
>
> if (AR_SREV_9300_20_OR_LATER(ah)) {
>   btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
>   btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9300;
>   btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9300;
>   btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9300;
>  } else if (AR_SREV_9280_20_OR_LATER(ah)) {
>   btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9280;
>   btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9280;
>   if (AR_SREV_9285(ah)) {
>    btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
>    btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9285;
>   } else {
>    btcoex_hw->scheme = ATH_BTCOEX_CFG_2WIRE;
>   }
>
> Regards
> Sandeep
>

[ath9k-devel] AR9287; BT Coexistence with 3-wire

[sandeep suresh]

Sure Mr. Adrian...that will be of great help.
As AR9287 supports both 2-wire and 3-wire, we thought 3-wire can be used.
Regards
Sandeep.


________________________________
From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org> 
Sent: Thursday, 21 March 2013 10:45 AM
Subject: Re: AR9287; BT Coexistence with 3-wire

I'll have to check this tomorrow.

It depends on what kind of BT chip was put on the AR9287 combo board
that you have. And I don't know whether it uses 2 wire or 3 wire.

There's a whole bunch of functions in the reference driver HAL which
tune the BT coexistence parameters. I'll see if I can dig that up too.



Adrian

On 20 March 2013 22:07, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello All,
>? ? In ath9k, only BT co-existence for 2-wire interface is selected for
> AR9287. Please refer to the code section below in btcoex.c. Does that mean
> the 3-wire interface based drivers available for AR9285 and AR9300+ cannot
> be used for AR9287?
>
> if (AR_SREV_9300_20_OR_LATER(ah)) {
>? btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
>? btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9300;
>? btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9300;
>? btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9300;
>? } else if (AR_SREV_9280_20_OR_LATER(ah)) {
>? btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9280;
>? btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9280;
>? if (AR_SREV_9285(ah)) {
>? ? btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
>? ? btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9285;
>? } else {
>? ? btcoex_hw->scheme = ATH_BTCOEX_CFG_2WIRE;
>? }
>
> Regards
> Sandeep
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130321/5a67dc76/attachment.htm 

[ath9k-devel] AR9287; BT Coexistence with 3-wire

[Adrian Chadd]

Hi,

It depends upon the bluetooth device it's attached to.

I think it's attached to an AR3011, and that may only support 2 wire.


Adrian

On 21 March 2013 00:06, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Sure Mr. Adrian...that will be of great help.
> As AR9287 supports both 2-wire and 3-wire, we thought 3-wire can be used.
> Regards
> Sandeep.
>
> From: Adrian Chadd <adrian@freebsd.org>
> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Sent: Thursday, 21 March 2013 10:45 AM
> Subject: Re: AR9287; BT Coexistence with 3-wire
>
> I'll have to check this tomorrow.
>
> It depends on what kind of BT chip was put on the AR9287 combo board
> that you have. And I don't know whether it uses 2 wire or 3 wire.
>
> There's a whole bunch of functions in the reference driver HAL which
> tune the BT coexistence parameters. I'll see if I can dig that up too.
>
>
>
> Adrian
>
> On 20 March 2013 22:07, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>> Hello All,
>>    In ath9k, only BT co-existence for 2-wire interface is selected for
>> AR9287. Please refer to the code section below in btcoex.c. Does that mean
>> the 3-wire interface based drivers available for AR9285 and AR9300+ cannot
>> be used for AR9287?
>>
>> if (AR_SREV_9300_20_OR_LATER(ah)) {
>>  btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
>>  btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9300;
>>  btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9300;
>>  btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9300;
>>  } else if (AR_SREV_9280_20_OR_LATER(ah)) {
>>  btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9280;
>>  btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9280;
>>  if (AR_SREV_9285(ah)) {
>>    btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
>>    btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9285;
>>  } else {
>>    btcoex_hw->scheme = ATH_BTCOEX_CFG_2WIRE;
>>  }
>>
>> Regards
>> Sandeep
>>
>
>

[ath9k-devel] AR9287; BT Coexistence with 3-wire

[sandeep suresh]

Hello Mr.Adrian,
????Thanks for your response.
?
But with only 2-wire interface, as I understand there are no weights register that can be configured for WiFi and BT? The only means of control is by the BT_ACTIVITY signal. All the following functions in ath9k related to weights and stomp type are handled for 3-wire interface:
a. ath9k_hw_btcoex_bt_stomp()
b. ath_init_btcoex_timer()
c. ath9k_hw_btcoex_set_weight()
?
The co-existence that we are planning to use is between a 802.15.4 radio on 2.4GHz and the WiFi module AR9287 module also at the same frequency and on the same board.?And we wanted to look at 3-wire interface as it has more sophisticated control based on stomp_type, weights allocation, priority (BT_PRIORITY) etc. Please advise suitably.
?
Thanks & regards
Sandeep.

________________________________
From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org> 
Sent: Thursday, 21 March 2013 6:43 PM
Subject: Re: AR9287; BT Coexistence with 3-wire

Hi,

It depends upon the bluetooth device it's attached to.

I think it's attached to an AR3011, and that may only support 2 wire.


Adrian

On 21 March 2013 00:06, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Sure Mr. Adrian...that will be of great help.
> As AR9287 supports both 2-wire and 3-wire, we thought 3-wire can be used.
> Regards
> Sandeep.
>
> From: Adrian Chadd <adrian@freebsd.org>
> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Sent: Thursday, 21 March 2013 10:45 AM
> Subject: Re: AR9287; BT Coexistence with 3-wire
>
> I'll have to check this tomorrow.
>
> It depends on what kind of BT chip was put on the AR9287 combo board
> that you have. And I don't know whether it uses 2 wire or 3 wire.
>
> There's a whole bunch of functions in the reference driver HAL which
> tune the BT coexistence parameters. I'll see if I can dig that up too.
>
>
>
> Adrian
>
> On 20 March 2013 22:07, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>> Hello All,
>>? ? In ath9k, only BT co-existence for 2-wire interface is selected for
>> AR9287. Please refer to the code section below in btcoex.c. Does that mean
>> the 3-wire interface based drivers available for AR9285 and AR9300+ cannot
>> be used for AR9287?
>>
>> if (AR_SREV_9300_20_OR_LATER(ah)) {
>>? btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
>>? btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9300;
>>? btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9300;
>>? btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9300;
>>? } else if (AR_SREV_9280_20_OR_LATER(ah)) {
>>? btcoex_hw->btactive_gpio = ATH_BTACTIVE_GPIO_9280;
>>? btcoex_hw->wlanactive_gpio = ATH_WLANACTIVE_GPIO_9280;
>>? if (AR_SREV_9285(ah)) {
>>? ? btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE;
>>? ? btcoex_hw->btpriority_gpio = ATH_BTPRIORITY_GPIO_9285;
>>? } else {
>>? ? btcoex_hw->scheme = ATH_BTCOEX_CFG_2WIRE;
>>? }
>>
>> Regards
>> Sandeep
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130322/db1d3792/attachment-0001.htm 

[ath9k-devel] AR9287; BT Coexistence with 3-wire

[Adrian Chadd]

Hi,


On 21 March 2013 22:32, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello Mr.Adrian,
>     Thanks for your response.
>
> But with only 2-wire interface, as I understand there are no weights
> register that can be configured for WiFi and BT? The only means of control
> is by the BT_ACTIVITY signal. All the following functions in ath9k related
> to weights and stomp type are handled for 3-wire interface:
> a. ath9k_hw_btcoex_bt_stomp()
> b. ath_init_btcoex_timer()
> c. ath9k_hw_btcoex_set_weight()
>
> The co-existence that we are planning to use is between a 802.15.4 radio on
> 2.4GHz and the WiFi module AR9287 module also at the same frequency and on
> the same board. And we wanted to look at 3-wire interface as it has more
> sophisticated control based on stomp_type, weights allocation, priority
> (BT_PRIORITY) etc. Please advise suitably.

I don't know what BT_PRIORITY gives you over 2-wire. But IIC the
weight and stomping happens regardless of whether it's 2-wire or
3-wire.

It's just that ath9k does it via static values if I recall, but our
reference driver dynamically adjusts the bluetooth values based on
what's going on in the air.
Hence my suggestion to start looking into that.

I haven't at all stared at the bluetooth code, I'm sorry. I've been
avoiding it (and for good reason!)



Adrian

[ath9k-devel] AR9287 Register state after ath9k_hw_reset()

[sandeep suresh]

Hello All,
     After the execution of the function ath9k_hw_reset() function, what will be the status of the hardware registers in AR9287? 
     Let us say we had set the GPIO Control & direction registers and also other control registers are initialized. If there is an execution of the ath9k_hw_reset(), will the hardware registers maintain their values before and after calling this function? If there is a loss, rather than initializing multiple function, is there a single ath9k_ function that can be called to restore the hardware registers?

THanks & regards
Sandeep Suresh.

[ath9k-devel] AR9287 Register state after ath9k_hw_reset()

[Adrian Chadd]

Hi,

I think the GPIO registers aren't cleared after a reset, but the
initvals may end up overriding things.

You can always add some calls _in_ ath9k_hw_reset() to restore the
hardware registers that you're after. That's what it does for other
things that need to persist through a hardware reset.


-a


On 18 April 2014 01:22, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello All,
>      After the execution of the function ath9k_hw_reset() function, what will be the status of the hardware registers in AR9287?
>      Let us say we had set the GPIO Control & direction registers and also other control registers are initialized. If there is an execution of the ath9k_hw_reset(), will the hardware registers maintain their values before and after calling this function? If there is a loss, rather than initializing multiple function, is there a single ath9k_ function that can be called to restore the hardware registers?
>
> THanks & regards
> Sandeep Suresh.

[ath9k-devel] AR9287 Register state after ath9k_hw_reset()

[sandeep suresh]

Hello Adrian,
????Thanks for your response. I have noticed the following and wanted to understand if this is normal behavior; please help. ath9k is configured? as a WiFi client. ?I instrumented the code and printed whenever ath9k_hw_reset() is called and the function calling the ath9k_hw_reset() function. AFter calling the wpa_supplicant package to enroll to the WiFi AP, I get the following debug messages:
?
Sandeep reset called from ath9k_start()
Sandeep: called from ath9k_hw_reset()
Sandeep reset called from ath_set_channel()
Sandeep: called from ath9k_hw_reset()
Sandeep reset called from ath_radio_disable()
Sandeep: called from ath9k_hw_reset()
root at wifi-client# Sandeep reset called from ath_radio_enable()
Sandeep: called from ath9k_hw_reset()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep: called from ath9k_hw_reset()
Sandeep reset called from ath_radio_disable()
Sandeep: called from ath9k_hw_reset()
Sandeep reset called from ath_radio_enable()
Sandeep: called from ath9k_hw_reset()
Sandeep reset called from ath_set_channel()
Sandeep reset called from ath_set_channel()
Sandeep: called from ath9k_hw_reset()
?
Regards
Sandeep Suresh
?

From: Adrian Chadd <adrian@freebsd.org>
To: sandeep suresh <sandeep.suresh@yahoo.co.in> 
Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org> 
Sent: Saturday, 26 April 2014 4:04 AM
Subject: Re: AR9287 Register state after ath9k_hw_reset()


Hi,

I think the GPIO registers aren't cleared after a reset, but the
initvals may end up overriding things.

You can always add some calls _in_ ath9k_hw_reset() to restore the
hardware registers that you're after. That's what it does for other
things that need to persist through a hardware reset.


-a



On 18 April 2014 01:22, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello All,
>? ? ? After the execution of the function ath9k_hw_reset() function, what will be the status of the hardware registers in AR9287?
>? ? ? Let us say we had set the GPIO Control & direction registers and also other control registers are initialized. If there is an execution of the ath9k_hw_reset(), will the hardware registers maintain their values before and after calling this function? If there is a loss, rather than initializing multiple function, is there a single ath9k_ function that can be called to restore the hardware registers?
>
> THanks & regards
> Sandeep Suresh.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140430/1456b647/attachment.htm 

[ath9k-devel] AR9287 Register state after ath9k_hw_reset()

[Adrian Chadd]

Yup, that's right. It's doing a scan.


-a


On 30 April 2014 01:57, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello Adrian,
>     Thanks for your response. I have noticed the following and wanted to
> understand if this is normal behavior; please help. ath9k is configured  as
> a WiFi client.  I instrumented the code and printed whenever
> ath9k_hw_reset() is called and the function calling the ath9k_hw_reset()
> function. AFter calling the wpa_supplicant package to enroll to the WiFi AP,
> I get the following debug messages:
>
> Sandeep reset called from ath9k_start()
> Sandeep: called from ath9k_hw_reset()
> Sandeep reset called from ath_set_channel()
> Sandeep: called from ath9k_hw_reset()
> Sandeep reset called from ath_radio_disable()
> Sandeep: called from ath9k_hw_reset()
> root at wifi-client# Sandeep reset called from ath_radio_enable()
> Sandeep: called from ath9k_hw_reset()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep: called from ath9k_hw_reset()
> Sandeep reset called from ath_radio_disable()
> Sandeep: called from ath9k_hw_reset()
> Sandeep reset called from ath_radio_enable()
> Sandeep: called from ath9k_hw_reset()
> Sandeep reset called from ath_set_channel()
> Sandeep reset called from ath_set_channel()
> Sandeep: called from ath9k_hw_reset()
>
> Regards
> Sandeep Suresh
>
>
> From: Adrian Chadd <adrian@freebsd.org>
> To: sandeep suresh <sandeep.suresh@yahoo.co.in>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Sent: Saturday, 26 April 2014 4:04 AM
> Subject: Re: AR9287 Register state after ath9k_hw_reset()
>
> Hi,
>
> I think the GPIO registers aren't cleared after a reset, but the
> initvals may end up overriding things.
>
> You can always add some calls _in_ ath9k_hw_reset() to restore the
> hardware registers that you're after. That's what it does for other
> things that need to persist through a hardware reset.
>
>
> -a
>
>
> On 18 April 2014 01:22, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
>> Hello All,
>>      After the execution of the function ath9k_hw_reset() function, what
>> will be the status of the hardware registers in AR9287?
>>      Let us say we had set the GPIO Control & direction registers and also
>> other control registers are initialized. If there is an execution of the
>> ath9k_hw_reset(), will the hardware registers maintain their values before
>> and after calling this function? If there is a loss, rather than
>> initializing multiple function, is there a single ath9k_ function that can
>> be called to restore the hardware registers?
>>
>> THanks & regards
>> Sandeep Suresh.
>
>

[ath9k-devel] Any WiFi Alliance Certification violation with WiFi Bluetooth Coexistence?

[sandeep suresh]

Hello All,
Just wanted to understand, if there will be any specific requirements that needs to be met for passing the WiFi Alliance certification when coexistence is enabled? Because WiFi will be stompted by "x" ms that can be few 10s of milliseconds. Have anyone come across this?Or is it nothing to be worried about and a standard feature of the WiFi chipset?
Thanks & regards
Sandeep.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140514/a7effe8a/attachment.htm 

[ath9k-devel] WiFi Alliance certification requirements for WiFi Bluetooth coexistence

[sandeep suresh]

Hello All,
Just wanted to understand, if there will be any specific requirements that needs to be met for passing the WiFi Alliance certification when coexistence is enabled? Because WiFi will be stompted by "x" ms that can be few 10/100s of milliseconds. The stomp duration depends on the duration for which BT_ACTIVE is asserted for 2-wire coexistence. Have anyone come across this?Or is it nothing to be worried about and a standard feature of the WiFi chipset?
Thanks & regards
Sandeep.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140515/e477a6ee/attachment-0001.htm 

[ath9k-devel] WiFi Alliance certification requirements for WiFi Bluetooth coexistence

[Adrian Chadd]

i unfortunately don't know the wifi alliance certification requirements. sorry.


-a


On 14 May 2014 18:30, sandeep suresh <sandeep.suresh@yahoo.co.in> wrote:
> Hello All,
> Just wanted to understand, if there will be any specific requirements that
> needs to be met for passing the WiFi Alliance certification when coexistence
> is enabled? Because WiFi will be stompted by "x" ms that can be few 10/100s
> of milliseconds. The stomp duration depends on the duration for which
> BT_ACTIVE is asserted for 2-wire coexistence. Have anyone come across
> this?Or is it nothing to be worried about and a standard feature of the WiFi
> chipset?
> Thanks & regards
> Sandeep.
>
>

[ath9k-devel] Distance measurement b/n WiFi client and AP in ath9k

[sandeep suresh]

Hello All,
    How can we measure the distance between a WiFi client and WiFi AP in a network? I am thinking in the perspective of Time of Flight functionality or deducing distance based on RSSI/LQI values.
As WiFi AP will be sending beacons every 100ms (or some configured period), from the WiFi CLient station, how can we get the RSSI/LQI values of the packets received from WiFi AP? Please let me know in software

Thanks & regards
Sandeep Suresh.