From: Johannes Berg <johannes@sipsolutions.net>
To: c_traja@qti.qualcomm.com, linux-wireless@vger.kernel.org
Cc: tamizhchelvam@codeaurora.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 2/4] cfg80211: Add new NL80211_CMD_SET_BTCOEX_PRIORITY to support BTCOEX
Date: Mon, 05 Dec 2016 15:49:13 +0100 [thread overview]
Message-ID: <1480949353.31788.27.camel@sipsolutions.net> (raw)
In-Reply-To: <1478610932-21954-3-git-send-email-c_traja@qti.qualcomm.com>
On Tue, 2016-11-08 at 18:45 +0530, c_traja@qti.qualcomm.com wrote:
>
> + * struct cfg80211_btcoex_priority - BTCOEX support frame type
> + *
> + * This structure defines the driver supporting frame types for
> BTCOEX
> + *
> + * @wlan_be_preferred: best effort frames preferred over bt traffic
> + * @wlan_bk_preferred: background frames preferred over bt traffic
> + * @wlan_vi_preferred: video frames preferred over bt traffic
> + * @wlan_vo_preferred: voice frames preferred over bt traffic
> + * @wlan_beacon_preferred: beacon preferred over bt traffic
> + * @wlan_mgmt_preferred: management frames preferred ovet bt traffic
typo: over
>
> /**
> + * wiphy_btcoex_support_flags
> + * This enum has the driver supported frame types for BTCOEX.
> + * @WIPHY_WLAN_BE_PREFERRED - Supports Best Effort frame for BTCOEX
> + * @WIPHY_WLAN_BK_PREFERRED - supports Background frame for BTCOEX
> + * @WIPHY_WLAN_VI_PREFERRED - supports Video frame for BTCOEX
> + * @WIPHY_WLAN_VO_PREFERRED - supports Voice frame for BTCOEX
> + * @WIPHY_WLAN_BEACON_PREFERRED - supports Beacon frame for BTCOEX
> + * @WIPHY_WLAN_MGMT_PREFERRED - supports Management frames for
> BTCOEX.
> + */
That's not making much sense to me?
> +/**
> + * enum wiphy_btcoex_priority - BTCOEX priority level
> + * This enum defines priority level for BTCOEX
> + * WIPHY_WLAN_PREFERRED_LOW - low priority frames over BT traffic
> + * WIPHY_WLAN_PREFERRED_HIGH - high priority frames over BT traffic
> + */
> +
> +enum wiphy_btcoex_priority {
> + WIPHY_WLAN_PREFERRED_LOW = false,
> + WIPHY_WLAN_PREFERRED_HIGH = true,
> +};
That false/true seems just strange.
> + * @btcoex_support_flags: This will have the driver supported
> + * frame types for BTCOEX. This value filled by using
> + * %enum wiphy_btcoex_support_flags while driver
> + * initialization.
The whole "will have" isn't really clear.
> + * @NL80211_ATTR_SET_BTCOEX_PRIORITY: nested attribute for driver
> supporting
> + * the BTCOEX. When used with
> %NL80211_CMD_SET_BTCOEX_PRIORITY it contains
> + * attributes according &enum nl80211_btcoex_priority to
> indicate
> + * which frame has high priority over BT.
There should be no "SET" in there.
> /**
> + * enum nl80211_btcoex_priority - BTCOEX parameter attributes
> + * This strcuture has enum values for driver supported wlan
> + * frame type for BTCOEX.
> + * @NL80211_WLAN_BE_PREFERRED - Best Effort frame
> + * @NL80211_WLAN_BK_PREFERRED - Background frame
> + * @NL80211_WLAN_VI_PREFERRED - Video frame
> + * @NL80211_WLAN_VO_PREFERRED - Voice frame
> + * @NL80211_WLAN_BEACON_PREFERRED - BEACON frame
> + * @NL80211_WLAN_MGMT_PREFERRED - MGMT frame
> + */
> +
> +enum nl80211_btcoex_priority {
> + __NL80211_WLAN_PREFERRED_INVALID,
> + NL80211_WLAN_BE_PREFERRED,
> + NL80211_WLAN_BK_PREFERRED,
> + NL80211_WLAN_VI_PREFERRED,
> + NL80211_WLAN_VO_PREFERRED,
> + NL80211_WLAN_BEACON_PREFERRED,
> + NL80211_WLAN_MGMT_PREFERRED,
> + __NL80211_WLAN_PREFERRED_LAST,
> + NL80211_WLAN_PREFERRED_MAX =
> + __NL80211_WLAN_PREFERRED_LAST - 1,
> +};
Wouldn't a bitmap be easier?
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-12-05 14:49 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 [this message]
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
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=1480949353.31788.27.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox