I'm glad you're looking into this in more depth!
On 4 April 2013 08:19, sandeep suresh <[email protected]> wrote:
> I understand that ATH_BTCOEX_CFG_2_WIRE, ATH_BTACTIVE_GPIO_9280 (GPIO6 as
> per btcoex.h) and ATH_WLANACTIVE_GPIO_9280 (GPIO5 as per btcoex.h) are used.
> I next started monitoring GPIO5 on oscillaoscope to see WLAN activity and I
> could see a lot of pulse trains. Next in order to simulate high priority BT
> traffic, I pulled the line GPIO6 high. But I did not see any change in WLAN
> activity as I could continue to see the pulse trains. My expectation was
> that there should not be any WLAN activity and hence no pulses. Please guide
> if I am missing anything?
Well, firstyl you need to ensure that the GPIO pin has been programmed
to be an input, and it's of the right bluetooth type. As I said
before, GPIO pins can be input, output; they can be connected via an
internal mux to a variety of "behaviours". Take a look at the gpio
configure code in ath9k to see more.
THen you need to ensure the bluetooth coexistence registers are
programmed so that btactive will correctly stomp wifi traffic.
THat's all I know for now. Sorry.