public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
	linux-kernel@vger.kernel.org, "Kevin Hayes\" <kevin@atheros.com>,
	\"Dan Tian\"" <Dan.Tian@atheros.com>
Subject: Linux Bluetooth Coexistence documentation in general and for ath9k
Date: Wed, 3 Mar 2010 16:43:37 -0800	[thread overview]
Message-ID: <43e72e891003031643u353c72dcj23bf429363a16ec8@mail.gmail.com> (raw)

Marcel, a question for you below.

The question of Bluetooth coexistence pops up here, on IRC and on bug
reports quite too often so I've stuffed what I could onto a page with
a few references / code and about ath9k's schemes for BT coexistence,
feel free to extend or correct:

http://wireless.kernel.org/en/users/Documentation/Bluetooth-coexistence
http://wireless.kernel.org/en/users/Drivers/ath9k/btcoex

I'm still not sure if "2-wire" and "3-wire" are generic terms and if
someone owns a trademark on them or what, but looking down the road I
think it would be nice to export this information through nl80211, if
a device supports any of these BT-coex schemes and if so, perhaps
display the current signal status of:

  * WLAN_ACTIVE
  * BT_PRIORITY
  * BT_STATE

I do wonder if this could be useful to network applets like network
manager/connman. The other BT coex schemes are BT specific it seems
and not sure if those devices can expose that information out and
inform userspace of certain events.

Marcel, does the BlueZ support exporting if certain bt-coex schemes
are supported like AFH, channel skipping, TDM, and also if they are
being used and details of that?

  Luis

             reply	other threads:[~2010-03-04  0:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  0:43 Luis R. Rodriguez [this message]
2010-03-04  0:59 ` Linux Bluetooth Coexistence documentation in general and for ath9k Bastien Nocera
2010-03-04  5:09   ` Luis R. Rodriguez
2010-03-04 10:18     ` Bastien Nocera
2010-03-04 15:10 ` Marcel Holtmann
2010-03-10 20:48   ` Pavel Machek
2010-03-10 22:11     ` Mike Tsai
2010-03-11  1:33       ` shy
2010-03-11  2:27         ` Mike Tsai

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=43e72e891003031643u353c72dcj23bf429363a16ec8@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=Dan.Tian@atheros.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.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