From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <35B17FE5076C7040809188FBE7913F983A1CC44471@SC1EXMB-MBCL.global.atheros.com> References: <43e72e891003031643u353c72dcj23bf429363a16ec8@mail.gmail.com> <1267715451.29510.20.camel@localhost.localdomain> <20100310204818.GF1394@ucw.cz> <35B17FE5076C7040809188FBE7913F983A1CC44471@SC1EXMB-MBCL.global.atheros.com> From: shy Date: Thu, 11 Mar 2010 09:33:27 +0800 Message-ID: Subject: Re: Linux Bluetooth Coexistence documentation in general and for ath9k To: Mike Tsai Cc: Pavel Machek , Marcel Holtmann , "Luis R. Rodriguez" , linux-wireless , linux-bluetooth , "linux-kernel@vger.kernel.org" , Dan Tian Content-Type: multipart/alternative; boundary=000e0cd25d8efa167704817c6712 List-ID: --000e0cd25d8efa167704817c6712 Content-Type: text/plain; charset=ISO-8859-1 Mike, This is done by controller. If host take the charge of channel map, then it must act as LMP role. Best regards shy 2010/3/11 Mike Tsai > Hi, > > I think host shall provide channel map to controller because it is > considered to be much more accurate than the channel map generated by > controller based on the RSSI reading. > > Mike > > -----Original Message----- > From: linux-bluetooth-owner@vger.kernel.org [mailto: > linux-bluetooth-owner@vger.kernel.org] On Behalf Of Pavel Machek > Sent: Wednesday, March 10, 2010 12:48 PM > To: Marcel Holtmann > Cc: Luis R. Rodriguez; linux-wireless; linux-bluetooth; > linux-kernel@vger.kernel.org; Dan Tian > Subject: Re: Linux Bluetooth Coexistence documentation in general and for > ath9k > > Hi! > > > > 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 > ... > > the only thing the host has control over is AFH channel map, and even > > modifying that is not really needed. The Bluetooth controller will do > > AFH automatically and it is on by default. We never switch that off > > actually. > > > > Normally the co-ex stuff is hard-wired between the Bluetooth and WiFi > > and thus out of control to the host OS. > > I believe that 'internal wifi, usb bluetooth' is still quite common > setup... > Pavel > -- > (english) http://www.livejournal.com/~pavelmachek > (cesky, pictures) > http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" > in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" > in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > --000e0cd25d8efa167704817c6712 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mike,
This is done by controller. If host take the charge of channel map= , then it must act=A0 as LMP role.
Best regards
shy


2010/3/11 Mike Tsai &l= t;Mike.Tsai@atheros.com>
Hi,

I think host shall provide channel map to controller because it is consider= ed to be much more accurate than the channel map generated by controller ba= sed on the RSSI reading.

Mike

-----Original Message-----
From: linux-blueto= oth-owner@vger.kernel.org [mailto:linux-bluetooth-owner@vger.kernel.org] On Behalf Of= Pavel Machek
Sent: Wednesday, March 10, 2010 12:48 PM
To: Marcel Holtmann
Cc: Luis R. Rodriguez; linux-wireless; linux-bluetooth; linux-kernel@vger.kernel.org; Dan Tian
Subject: Re: Linux Bluetooth Coexistence documentation in general and for a= th9k

Hi!

> > 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 p= age with
> > a few references / code and about ath9k's schemes for BT coex= istence,
> > feel free to extend or correct:
> >
> > http://wireless.kernel.org/en/users/Do= cumentation/Bluetooth-coexistence
> > http://wireless.kernel.org/en/users/Drivers/ath9k/btc= oex
> >
> > I'm still not sure if "2-wire" and "3-wire&quo= t; are generic terms and if
> > someone owns a trademark on them or what, but looking down the ro= ad 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:
> >
> > =A0 * WLAN_ACTIVE
> > =A0 * BT_PRIORITY
> > =A0 * BT_STATE
...
> the only thing the host has control over is AFH channel map, and even<= br> > modifying that is not really needed. The Bluetooth controller will do<= br> > AFH automatically and it is on by default. We never switch that off > actually.
>
> Normally the co-ex stuff is hard-wired between the Bluetooth and WiFi<= br> > and thus out of control to the host OS.

I believe that 'internal wifi, usb bluetooth' is still quite common=
setup...
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pav= el/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-blueto= oth" in
the body of a message to major= domo@vger.kernel.org
More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-blueto= oth" in
the body of a message to major= domo@vger.kernel.org
More majordomo info at =A0http://vger.kernel.org/majordomo-info.html

--000e0cd25d8efa167704817c6712--