Re: [PATCH 1/2] [RFC] cfg80211: configuration of Bluetooth coexistence mode

["Arend van Spriel" <arend@broadcom.com>]

On 02/25/13 14:07, Felix Fietkau wrote:
> On 2013-02-25 11:25 AM, Johannes Berg wrote:
>> On Mon, 2013-02-25 at 06:54 +0100, Felix Fietkau wrote:
>>
>>> Most devices have some kind of connection manager that has a high-level
>>> perspective of when it's fully connected (which includes DHCP/bootp).
>>> Why not just let that connection manager set a sane maximum network
>>> latency value via pm_qos network_latency and derive btcoex weight
>>> changing and multi-channel settings from that?
>>
>> Frankly, I don't think that's going to work well. We tried using the
>> pm_qos framework once and nothing ever used it. Android isn't going to
>> change to it, so we'd be stuck with hacks like setting pm_qos in
>> wpa_supplicant which is just as awkward.
> If only the connection manager gets changed to use it, that would
> already be enough. It doesn't have to be pushed into dhcp clients and
> other applications.

Reading back some slides about pm_qos it (from Intel OSTC ;-) ) seems to 
be intended to make kernel drivers aware of performance requirements in 
other kernel parts or user-space. Sounds like a match here although it 
is a one-to-many notification framework. Also not exactly what we want 
(I think).

Gr. AvS