Prev: ACPI / PM: Move ACPI video resume to a PM notifier
Next: [PATCH] i386: do a global tlb flush in S4 resume
From: Bastien Nocera on 3 Mar 2010 20:20
On Wed, 2010-03-03 at 16:43 -0800, Luis R. Rodriguez wrote:
> 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:
<snip>
> I do wonder if this could be useful to network applets like network
> manager/connman.

Not really. To me, it sounds like a "make it work" button. The kernel
bits of Bluetooth should already have an idea of when a device is
connected, so the kernel should be able to "do the right thing".

Having options over what "the right thing" is is probably a good idea
whilst the kinks are worked out from the default behaviour, but this is
not something that should be advertised to users.

> 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.

Cheers

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Marcel Holtmann on 4 Mar 2010 10:20
Hi Luis,

> 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?

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.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: ACPI / PM: Move ACPI video resume to a PM notifier
Next: [PATCH] i386: do a global tlb flush in S4 resume