From: sandeep suresh <sandeep.suresh@yahoo.co.in>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Register setting for 2-wire, 3-wire and MCI coexistence schemes
Date: Fri, 6 May 2016 08:13:16 +0000 (UTC) [thread overview]
Message-ID: <1416774340.201430.1462522396907.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: 1416774340.201430.1462522396907.JavaMail.yahoo.ref@mail.yahoo.com
Hello,By configuring which register in ath9k, the different schemes like: 2-wire, 3-wire or MCI based coexistence schemes between WiFi and Bluetooth is selected? In ath9k under btcoex.c, gpio.c, hw.c, init.c, did not find any configuration setting.Please help.Regards
Sandeep.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160506/f7eb43d5/attachment.htm
next parent reply other threads:[~2016-05-06 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1416774340.201430.1462522396907.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-06 8:13 ` sandeep suresh [this message]
2016-05-10 9:49 ` [ath9k-devel] Register setting for 2-wire, 3-wire and MCI coexistence schemes sandeep suresh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1416774340.201430.1462522396907.JavaMail.yahoo@mail.yahoo.com \
--to=sandeep.suresh@yahoo.co.in \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).