From: Tamizh chelvam <tamizhchelvam@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: c_traja@qti.qualcomm.com, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Re: [PATCH 2/4] cfg80211: Add new NL80211_CMD_SET_BTCOEX_PRIORITY to support BTCOEX
Date: Mon, 09 Jan 2017 15:40:57 +0530 [thread overview]
Message-ID: <6f9711ed6f6fe170b915b67a054b985b@codeaurora.org> (raw)
In-Reply-To: <1483623500.4394.18.camel@sipsolutions.net>
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.
Thanks,
Tamizh.
next prev parent reply other threads:[~2017-01-09 10:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 13:15 [PATCH 0/4] cfg80211: mac80211: BTCOEX feature support c_traja
2016-11-08 13:15 ` [PATCH 1/4] cfg80211: Add support to enable or disable btcoex c_traja
2016-12-05 14:46 ` Johannes Berg
2016-12-07 11:04 ` Tamizh chelvam
2016-11-08 13:15 ` [PATCH 2/4] cfg80211: Add new NL80211_CMD_SET_BTCOEX_PRIORITY to support BTCOEX c_traja
2016-12-05 14:49 ` Johannes Berg
2016-12-07 17:59 ` Tamizh chelvam
2016-12-13 16:09 ` Johannes Berg
2016-12-16 5:53 ` Tamizh chelvam
2016-12-16 9:37 ` Johannes Berg
2016-12-19 8:11 ` Tamizh chelvam
2017-01-02 10:48 ` Johannes Berg
2017-01-05 13:18 ` Tamizh chelvam
2017-01-05 13:38 ` Johannes Berg
2017-01-09 10:10 ` Tamizh chelvam [this message]
2017-01-09 10:36 ` Johannes Berg
2017-01-19 13:52 ` Tamizh chelvam
2016-11-08 13:15 ` [PATCH 3/4] mac80211: Add support to enable or disable btcoex c_traja
2016-11-08 13:15 ` [PATCH 4/4] mac80211: Add support to update btcoex priority value c_traja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6f9711ed6f6fe170b915b67a054b985b@codeaurora.org \
--to=tamizhchelvam@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=c_traja@qti.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).