linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: linux-wireless@vger.kernel.org,
	Avraham Stern <avraham.stern@intel.com>,
	Arik Nemtsov <arikx.nemtsov@intel.com>,
	Ilan Peer <ilan.peer@intel.com>
Subject: Re: [PATCH] cfg80211: Allow GO concurrent relaxation after BSS disconnetion
Date: Fri, 24 Apr 2015 12:32:34 +0200	[thread overview]
Message-ID: <1429871554.1852.32.camel@sipsolutions.net> (raw)
In-Reply-To: <1427720905-30872-1-git-send-email-emmanuel.grumbach@intel.com>

On Mon, 2015-03-30 at 16:08 +0300, Emmanuel Grumbach wrote:
> From: Avraham Stern <avraham.stern@intel.com>
> 
> If P2P GO was allowed on a channel because of the GO concurrent
> relaxation and additional station interface associated to an AP on
> the same channel or the same UNII band, and the station interface
> disconnected from the AP, allow the P2P GO to stay on that channel
> unless the channel is marked as indoor only and the device is not
> operating in an indoor environment.

I'm not really sure what to do with this - this neither explains why
this is needed nor why it's actually allowed to do it.

> +               if (wdev->iftype == NL80211_IFTYPE_STATION &&
> +                   netif_running(wdev->netdev) && wdev->current_bss)

having a current_bss implies running

> +               if (wdev->iftype == NL80211_IFTYPE_P2P_GO &&
> wdev->netdev &&
> +                   netif_running(wdev->netdev) &&
> wdev->beacon_interval &&
> +                   !(chan->flags & IEEE80211_CHAN_INDOOR_ONLY))
> +                       other_chan = wdev->chandef.chan;

that "wdev->netdev" check is also useless, iftype==P2P_GO must have a
netdev.
netif_running() is probably also useless since wdev->beacon_interval
implies it.

This patch also doesn't really do exactly what you said it does - it
doesn't just allow that GO to be running but it also allows more to be
started up there... Not sure if that's desired, but it should be
documented (again, with the reasons for it)

johannes


      reply	other threads:[~2015-04-24 10:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 13:08 [PATCH] cfg80211: Allow GO concurrent relaxation after BSS disconnetion Emmanuel Grumbach
2015-04-24 10:32 ` Johannes Berg [this message]

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=1429871554.1852.32.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arikx.nemtsov@intel.com \
    --cc=avraham.stern@intel.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ilan.peer@intel.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).