linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Purushottam Kushwaha <pkushwah@qti.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, jouni@qca.qualcomm.com,
	usdutt@qti.qualcomm.com, amarnath@qca.qualcomm.com,
	djindal@qti.qualcomm.com
Subject: Re: [PATCH v5] cfg80211: Provision to allow the support for different beacon intervals
Date: Thu, 11 Aug 2016 15:08:36 +0200	[thread overview]
Message-ID: <1470920916.12075.15.camel@sipsolutions.net> (raw)
In-Reply-To: <1470916154-18821-1-git-send-email-pkushwah@qti.qualcomm.com>


> +static bool diff_beacon_interval_supported(struct wiphy *wiphy, u16
> types,
> +					   u32 beacon_int)
> +{
> +	const struct ieee80211_iface_combination *c;
> +	u16 all_types;
> +	int i, j;
> +
> +	for (i = 0; i < wiphy->n_iface_combinations; i++) {
> +		c = &wiphy->iface_combinations[i];
> +
> +		if (!c->diff_beacon_int_gcd ||
> +		    (beacon_int % c->diff_beacon_int_gcd))
> +			continue;
> +
> +		all_types = 0;
> +		for (j = 0; j < c->n_limits; j++)
> +			all_types |= c->limits[j].types;
> +
> +		if (all_types & types)
> +			return true;
> +	}
> +
> +	return false;
> +}

This seems odd. Shouldn't it use cfg80211_iter_combinations()? Might
need some additional helper to understand which interface types are
used right now - seems we mostly moved that to mac80211, but for this
case it should probably stay in cfg80211? Or should it?

johannes

  reply	other threads:[~2016-08-11 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 11:49 [PATCH v5] cfg80211: Provision to allow the support for different beacon intervals Purushottam Kushwaha
2016-08-11 13:08 ` Johannes Berg [this message]
2016-08-11 15:34   ` Undekari, Sunil Dutt

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=1470920916.12075.15.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=amarnath@qca.qualcomm.com \
    --cc=djindal@qti.qualcomm.com \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkushwah@qti.qualcomm.com \
    --cc=usdutt@qti.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).