[PATCH 2/4] cfg80211: Add new NL80211_CMD_SET_BTCOEX_PRIORITY to support BTCOEX

Tamizh chelvam tamizhchelvam at codeaurora.org
Mon Jan 9 02:10:57 PST 2017

Hi Johannes,

Thank you for the reply.

On 2017-01-05 19:08, Johannes Berg wrote:
>> > IOW - why have all these bits rather than just one?
>> Hardware supports data across all the access categories, this is
>> just  meant for prioritising the traffic. f.e, If the fw/target has
>> both wlan and bt traffic queued and if VO is  set as priority, then
>> wlan VO packets will be pushed out of the radio first and then the bt
>> traffic.
> Exactly. So as far as *capabilities* are concerned, why do we need so
> many bits?
Is it fine to have something like this

1) We can have this btcoex_priority value as a optional value in btcoex 
enable command like below

iw phyX btcoex_state <enable| disable> [prirority(vendor spcific value)]

2) Or we can have seperate command for btcoex_priority as below

iw phyX set btcoex_priority <priority (vendor spcific value)>

Hopefully this will get rid off all the nl80211 bits.

Kindly suggest your thoughts.


More information about the ath10k mailing list