From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-we0-f170.google.com ([74.125.82.170]:64263 "EHLO mail-we0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758971Ab3DHSjW (ORCPT ); Mon, 8 Apr 2013 14:39:22 -0400 Received: by mail-we0-f170.google.com with SMTP id z2so4992954wey.1 for ; Mon, 08 Apr 2013 11:39:20 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1365433751.96373.YahooMailNeo@web193505.mail.sg3.yahoo.com> References: <515A0847.7000306@gmail.com> <1365088789.89181.YahooMailNeo@web193504.mail.sg3.yahoo.com> <1365131280.68622.YahooMailNeo@web193506.mail.sg3.yahoo.com> <1365148844.61162.YahooMailNeo@web193503.mail.sg3.yahoo.com> <1365152761.13005.YahooMailNeo@web193505.mail.sg3.yahoo.com> <20830.46610.23754.783231@gargle.gargle.HOWL> <1365175482.75704.YahooMailNeo@web193505.mail.sg3.yahoo.com> <1365346495.79596.YahooMailNeo@web193506.mail.sg3.yahoo.com> <1365398445.32740.YahooMailNeo@web193504.mail.sg3.yahoo.com> <1365413949.24195.YahooMailNeo@web193502.mail.sg3.yahoo.com> <1365433751.96373.YahooMailNeo@web193505.mail.sg3.yahoo.com> Date: Mon, 8 Apr 2013 11:39:20 -0700 Message-ID: (sfid-20130408_203926_536471_99A9C12B) Subject: Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior From: Adrian Chadd To: sandeep suresh Cc: Sujith Manoharan , ath9k-devel , "linux-wireless@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: yes, there's GPIO MUX modes for: * RX clear (but I think this "Wlan active" pin is likely triggering on RX_CLEAR, which I think gets asserted for both TX and RX busy. I'll have to check. * TX active Check the GPIO MUX pin definitions to see. But if I understand this right, if you have the correct btcoex setup and GPIO pins working, then stomping traffic will stomp both TX and RX.. Adrian From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrian Chadd Date: Mon, 8 Apr 2013 11:39:20 -0700 Subject: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior In-Reply-To: <1365433751.96373.YahooMailNeo@web193505.mail.sg3.yahoo.com> References: <515A0847.7000306@gmail.com> <1365088789.89181.YahooMailNeo@web193504.mail.sg3.yahoo.com> <1365131280.68622.YahooMailNeo@web193506.mail.sg3.yahoo.com> <1365148844.61162.YahooMailNeo@web193503.mail.sg3.yahoo.com> <1365152761.13005.YahooMailNeo@web193505.mail.sg3.yahoo.com> <20830.46610.23754.783231@gargle.gargle.HOWL> <1365175482.75704.YahooMailNeo@web193505.mail.sg3.yahoo.com> <1365346495.79596.YahooMailNeo@web193506.mail.sg3.yahoo.com> <1365398445.32740.YahooMailNeo@web193504.mail.sg3.yahoo.com> <1365413949.24195.YahooMailNeo@web193502.mail.sg3.yahoo.com> <1365433751.96373.YahooMailNeo@web193505.mail.sg3.yahoo.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org yes, there's GPIO MUX modes for: * RX clear (but I think this "Wlan active" pin is likely triggering on RX_CLEAR, which I think gets asserted for both TX and RX busy. I'll have to check. * TX active Check the GPIO MUX pin definitions to see. But if I understand this right, if you have the correct btcoex setup and GPIO pins working, then stomping traffic will stomp both TX and RX.. Adrian