Hello Mr.Adrian and Mr.Sujith,
As I understand WLAN_ACTIVE is asserted whenever either WLAN_TX or WLAN_Rx
is asserted. Hence the pulse trains that I am observing during BT_ACTIVE
asserted might be those corresponding to WLAN_RX. Hence is it possible to route
the status of WLAN_TX and WLAN_RX via two separate GPIO lines for monitoring on
oscilloscope rather than a single GPIO line for WLAN_ACTIVE (= WLAN_TX +
WLAN_RX)?
Thanks & regards
Sandeep.
________________________________
From: sandeep suresh <sandeep.sur...@yahoo.co.in>
To: Adrian Chadd <adr...@freebsd.org>
Cc: Sujith Manoharan <suj...@msujith.org>; ath9k-devel
<ath9k-devel@lists.ath9k.org>; "linux-wirel...@vger.kernel.org"
<linux-wirel...@vger.kernel.org>
Sent: Monday, 8 April 2013 3:09 PM
Subject: Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior
Mr.Adrian,
Thanks for your mail. In FreeBSD, where can I find the 2-wire/3-wire pin
definitions, weight register settings, stomping etc. For AR9287, Should I need
to look at AR5416 under /sys/dev/ath/ath_hal?
Regards
Sandeep.
________________________________
From: Adrian Chadd <adr...@freebsd.org>
To: sandeep suresh <sandeep.sur...@yahoo.co.in>
Cc: Sujith Manoharan <suj...@msujith.org>; ath9k-devel
<ath9k-devel@lists.ath9k.org>; "linux-wirel...@vger.kernel.org"
<linux-wirel...@vger.kernel.org>
Sent: Monday, 8 April 2013 2:30 PM
Subject: Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior
Also, I don't know why you're writing both config values out to
BTCOEX_MODE and BTCOEX_MODE2.
MODE2 has a _totally_ different register layout to AR_BT_COEX_MODE.
Please make sure you read the register definitions in the header
file(s) before you write values out. :-)
Adrian
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
