linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: c_traja@qti.qualcomm.com, linux-wireless@vger.kernel.org
Cc: ath10k@lists.infradead.org
Subject: Re: [PATCHv2 3/4] cfg80211: Add Support set btcoex priority value
Date: Thu, 02 Mar 2017 09:50:59 +0100	[thread overview]
Message-ID: <1488444659.8390.8.camel@sipsolutions.net> (raw)
In-Reply-To: <1488029873-14600-4-git-send-email-c_traja@qti.qualcomm.com>

Is there much point in having 4 rather than just 2 patches?


> +	int     (*set_btcoex)(struct wiphy *wiphy, bool enabled,
> +			      int btcoex_priority);

Shouldn't that be u32 as a bitmap?

> +	bool btcoex_priority_support;

Why not use an extended nl80211 feature flag directly?

> + * @NL80211_ATTR_BTCOEX_PRIORITY: This is for the driver which
> + *     support btcoex priority feature. It used with
> %NL80211_CMD_SET_BTCOEX.
> + *     This will have u32 BITMAP value which represents
> + *     frame(bk, be, vi, vo, mgmt, beacon) type and that will have
> more
> + *     priority than a BT traffic.

I think you need to define the bits somewhere in an enum - i.e. which
one is VO, VI, ...

> +	int btcoex_priority = -1;

That -1 is pretty useless, if the driver doesn't support it, hopefully
it won't look at the value at all?

johannes

  parent reply	other threads:[~2017-03-02  8:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25 13:37 [PATCHv2 0/4] cfg80211: mac80211: BTCOEX feature support c_traja
2017-02-25 13:37 ` [PATCHv2 1/4] cfg80211: Add support to enable or disable btcoex c_traja
2017-02-25 14:48   ` kbuild test robot
2017-02-25 14:48   ` kbuild test robot
2017-03-02  8:45   ` Johannes Berg
2017-03-02 11:49     ` Raja, Tamizh Chelvam
2017-02-25 13:37 ` [PATCHv2 2/4] mac80211: " c_traja
2017-02-25 13:37 ` [PATCHv2 3/4] cfg80211: Add Support set btcoex priority value c_traja
2017-02-25 15:12   ` kbuild test robot
2017-03-02  8:50   ` Johannes Berg [this message]
2017-03-02 11:48     ` Raja, Tamizh Chelvam
2017-03-02 12:15       ` Johannes Berg
2017-03-02 13:08         ` Raja, Tamizh Chelvam
2017-03-02 13:43           ` Johannes Berg
2017-03-02  8:51   ` Johannes Berg
2017-02-25 13:37 ` [PATCHv2 4/4] mac80211: Add support to set/update " c_traja
2017-02-25 14:41 ` [PATCHv2 0/4] cfg80211: mac80211: BTCOEX feature support Arend Van Spriel
2017-02-27 10:33   ` Raja, Tamizh Chelvam

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=1488444659.8390.8.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath10k@lists.infradead.org \
    --cc=c_traja@qti.qualcomm.com \
    --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).