From: Johannes Berg <johannes@sipsolutions.net>
To: "Raja, Tamizh Chelvam" <c_traja@qti.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCHv2 3/4] cfg80211: Add Support set btcoex priority value
Date: Thu, 02 Mar 2017 13:15:58 +0100 [thread overview]
Message-ID: <1488456958.8390.15.camel@sipsolutions.net> (raw)
In-Reply-To: <b55e902d1a5445feb3058cee1118ae39@aphydexm01f.ap.qualcomm.com>
> > I think you need to define the bits somewhere in an enum - i.e.
> > which one is VO,
> > VI, ...
> >
>
> [Tamizh] ok sure. Is this for documentation purpose or do you want me
> to use that enum for something else?
Well I think you should check in cfg80211 that no bits not defined in
the enum are used, and then in the driver you need to use that enum to
translate to the firmware API, right?
johannes
next prev parent reply other threads:[~2017-03-02 13:31 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
2017-03-02 11:48 ` Raja, Tamizh Chelvam
2017-03-02 12:15 ` Johannes Berg [this message]
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=1488456958.8390.15.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).