On Wed, 2017-04-12 at 07:08 +0000, Tamizh Chelvam Raja wrote:
> >
> > So you make a distinction between WMM ACs, but what about the
> > different
> > types/profiles of BT traffic?
> >
>
> [Tamizh] There will be BT high and BT low traffic. It will be decided
> by BT module. Firmware internally checks BT low traffic with wlan
> traffic. If we enable some of wlan frames as high priority, those
> frames will have more priority than BT low traffic.
That ("firmware internally..." etc.) really sounds more like an
argument *not* to apply this patch ...
Everyone has their favourite BT coex control. We could possibly
implement this in our driver, but I'm not sure we'd *want* to, since
it's so far from what we actually do today.
Do we really need more than toggling it on/off?
Actually, I probably should've asked this much earlier - but what use
cases do you see for this? What can a user, or userspace application
like NM, really try to set here? It seems the use cases for this would
be rather constrained?
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
