[PATCH v2] ath10k: Debugfs entry to enable/disable WLAN&Blutooth Coexist feature
yanbol at qca.qualcomm.com
Tue Jun 2 17:18:01 PDT 2015
> -----Original Message-----
> From: Jakub Kiciński [mailto:moorray3 at wp.pl]
> Sent: Tuesday, June 02, 2015 2:39 AM
> To: Li, Yanbo
> Cc: Valo, Kalle; dreamfly281 at gmail.com; ath10k at lists.infradead.org; linux-
> wireless at vger.kernel.org
> Subject: Re: [PATCH v2] ath10k: Debugfs entry to enable/disable
> WLAN&Blutooth Coexist feature
> On Thu, 28 May 2015 12:19:05 -0700, Yanbo Li wrote:
> > As some radio have no connection with BT modules, enable the
> > WLAN/Bluetooth
> > coexist(BTC) feature will has some side effect if the radio's GPIO
> > connect with any other HW modules. Add the control switcher
> > "btc_feature" at debugfs and set the feature as disable by default to avoid
> such case.
> > To enable this feature, execute:
> > echo 1 > /sys/kernel/debug/ieee80211/phyX/ath10k/btc_feature
> > To disable:
> > echo 0 > /sys/kernel/debug/ieee80211/phyX/ath10k/btc_feature
> > Signed-off-by: Yanbo Li <yanbol at qca.qualcomm.com>
> IMHO common API for disabling/enabling btcoex is something we would all
> benefit from and easy enough to implement properly. Burying it in driver-
> specific debugfs is less than appropriate.
> I seem to recall there were plans to discuss btcoex at one of the linux-
> wireless summits. If the consensus was to leave it in debugfs then I
> apologize for the noise ;)
Thanks for your comments, agree with a general BTcoex interface will be good for lots of wlan chip/driver.
It worth to be consider to implement such framework in future.
More information about the ath10k