linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jouni@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, Peng Xu <pxu@qca.qualcomm.com>
Subject: Re: [PATCH] cfg80211: Add HT and VHT information in start_ap
Date: Tue, 16 Aug 2016 08:52:47 +0200	[thread overview]
Message-ID: <1471330367.16783.23.camel@sipsolutions.net> (raw)
In-Reply-To: <1471284424-12142-1-git-send-email-jouni@qca.qualcomm.com>

On Mon, 2016-08-15 at 21:07 +0300, Jouni Malinen wrote:
> From: Peng Xu <pxu@qca.qualcomm.com>
> 
> Add HT and VHT information in struct cfg80211_ap_settings when
> starting ap so that driver does not need to parse IE to obtain
> the information.

> +enum ht_vht_support {
> +	HT_VHT_DISABLED,
> +	HT_VHT_ENABLED,
> +	HT_VHT_NOT_INDICATED
> +};

So if you get HT_VHT_NOT_INDICATED in the driver, don't you *still*
have to parse the IEs?

Arguably, cfg80211 could know itself by parsing though, so it could
already fall back to that, no?

But if you do that, you already need the parsing code, so then perhaps
it would make sense to just always use the parsing in cfg80211? Or
export a parsing function to use in driver(s)?

> @@ -719,6 +729,11 @@ struct cfg80211_ap_settings {
>  	bool p2p_opp_ps;
>  	const struct cfg80211_acl_data *acl;
>  	bool pbss;
> +	enum ht_vht_support ht_enabled;
> +	enum ht_vht_support vht_enabled;
> +	enum ht_vht_support require_ht;
> +	enum ht_vht_support require_vht;
> +

(nit - extra blank line)

johannes

  reply	other threads:[~2016-08-16  6:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 18:07 [PATCH] cfg80211: Add HT and VHT information in start_ap Jouni Malinen
2016-08-16  6:52 ` Johannes Berg [this message]
2016-08-16 12:34   ` Malinen, Jouni
2016-08-26  8:09     ` Johannes Berg
2016-09-12 10:09       ` Johannes Berg
2016-10-03 21:15         ` Malinen, Jouni
2016-10-04 13:25           ` Johannes Berg
2016-10-04 16:15             ` Malinen, Jouni
2016-10-13 13:12               ` Johannes Berg

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=1471330367.16783.23.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pxu@qca.qualcomm.com \
    /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).