From: Johannes Berg <johannes@sipsolutions.net>
To: Tamizh chelvam <tamizhchelvam@codeaurora.org>
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: Thu, 05 Jan 2017 14:38:20 +0100 [thread overview]
Message-ID: <1483623500.4394.18.camel@sipsolutions.net> (raw)
In-Reply-To: <a5521b4e246de90ed8526891c84a97e5@codeaurora.org>
> > 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?
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Tamizh chelvam <tamizhchelvam@codeaurora.org>
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: Thu, 05 Jan 2017 14:38:20 +0100 [thread overview]
Message-ID: <1483623500.4394.18.camel@sipsolutions.net> (raw)
In-Reply-To: <a5521b4e246de90ed8526891c84a97e5@codeaurora.org>
> > 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?
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-01-05 13:39 UTC|newest]
Thread overview: 38+ 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 ` c_traja
2016-11-08 13:15 ` [PATCH 1/4] cfg80211: Add support to enable or disable btcoex c_traja
2016-11-08 13:15 ` c_traja
2016-12-05 14:46 ` Johannes Berg
2016-12-05 14:46 ` Johannes Berg
2016-12-07 11:04 ` Tamizh chelvam
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-11-08 13:15 ` c_traja
2016-12-05 14:49 ` Johannes Berg
2016-12-05 14:49 ` Johannes Berg
2016-12-07 17:59 ` Tamizh chelvam
2016-12-07 17:59 ` Tamizh chelvam
2016-12-13 16:09 ` Johannes Berg
2016-12-13 16:09 ` Johannes Berg
2016-12-16 5:53 ` Tamizh chelvam
2016-12-16 5:53 ` Tamizh chelvam
2016-12-16 9:37 ` Johannes Berg
2016-12-16 9:37 ` Johannes Berg
2016-12-19 8:11 ` Tamizh chelvam
2016-12-19 8:11 ` Tamizh chelvam
2017-01-02 10:48 ` Johannes Berg
2017-01-02 10:48 ` Johannes Berg
2017-01-05 13:18 ` Tamizh chelvam
2017-01-05 13:18 ` Tamizh chelvam
2017-01-05 13:38 ` Johannes Berg [this message]
2017-01-05 13:38 ` Johannes Berg
2017-01-09 10:10 ` Tamizh chelvam
2017-01-09 10:10 ` Tamizh chelvam
2017-01-09 10:36 ` Johannes Berg
2017-01-09 10:36 ` Johannes Berg
2017-01-19 13:52 ` Tamizh chelvam
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 ` c_traja
2016-11-08 13:15 ` [PATCH 4/4] mac80211: Add support to update btcoex priority value c_traja
2016-11-08 13:15 ` 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=1483623500.4394.18.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=c_traja@qti.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tamizhchelvam@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.