From mboxrd@z Thu Jan 1 00:00:00 1970 From: sandeep suresh Date: Fri, 5 Apr 2013 11:08:00 +0800 (SGT) Subject: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior In-Reply-To: References: <515A0847.7000306@gmail.com> <1365088789.89181.YahooMailNeo@web193504.mail.sg3.yahoo.com> Message-ID: <1365131280.68622.YahooMailNeo@web193506.mail.sg3.yahoo.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Hello Mr.Adrian, ????Thanks for your mail. Regarding your comment below: ? "THen you need to ensure the bluetooth coexistence registers are programmed so that btactive will correctly stomp wifi traffic." ? Can you please elaborate on this? As I understand the concept of "stomping" is only in 3-wire coexistence; correct me if I am wrong. ? As mentioned earlier, the set-up we have is a PCB board with general purpose MCU controlling the 2-wire coexistence pins of AR9287. As there are other 2.4GHz radio (called PROP radio here) on the board, we want to ensure that both radios do not transmit at the same time which will result in collisions. Hence we want to build a co-operative coexistence approach so that when PROP radio is active (by asserting BT_ACTIVE), AR9287 has to buffer transmissions and allow PROP radio to be active. Only when?PROP radio?is inactive (BT_ACTIVE is deasserted), only then WiFi can be active. Hope this is achievable? ? Thanks & Regards Sandeep. ________________________________ From: Adrian Chadd To: sandeep suresh Cc: "linux-wireless at vger.kernel.org" ; ath9k-devel Sent: Thursday, 4 April 2013 11:36 PM Subject: Re: AR9287 ; 2-wire coexistence expected behavior Hi! I'm glad you're looking into this in more depth! On 4 April 2013 08:19, sandeep suresh 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. Ok, right. > 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. adrian -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130405/6ac67952/attachment.htm