linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Ilan Peer <ilan.peer@intel.com>
Cc: linux-wireless@vger.kernel.org, ArikX Nemtsov <arik@wizery.com>
Subject: Re: [PATCH v10 2/3] cfg80211: Add API to change the indoor regulatory setting
Date: Thu, 5 Mar 2015 23:54:04 +0100	[thread overview]
Message-ID: <20150305225404.GB25035@wotan.suse.de> (raw)
In-Reply-To: <1425447127-22958-2-git-send-email-ilan.peer@intel.com>

On Wed, Mar 04, 2015 at 12:32:06AM -0500, Ilan Peer wrote:
> -int regulatory_hint_indoor_user(void)
> +int regulatory_hint_indoor(bool is_indoor, u32 portid)
>  {
> +	spin_lock(&reg_indoor_lock);
> +
> +	/* It is possible that more than one user space process is trying to
> +	 * configure the indoor setting. To handle such cases, clear the indoor
> +	 * setting in case that some process does not think that the device
> +	 * is operating in an indoor environment. In addition, if a user space
> +	 * process indicates that it is controlling the indoor setting, save its
> +	 * portid, i.e., make it the owner.
> +	 */
> +	reg_is_indoor = is_indoor;
> +	if (reg_is_indoor) {
> +		if (!reg_is_indoor_portid)
> +			reg_is_indoor_portid = portid;
> +	} else {
> +		reg_is_indoor_portid = 0;
> +	}
>  
> +	spin_unlock(&reg_indoor_lock);
>  
> -	reg_is_indoor = true;
> +	if (!is_indoor)
> +		reg_check_channels();
>  
>  	return 0;
>  }

OK lets start with this...

 Luis

  reply	other threads:[~2015-03-05 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  5:32 [PATCH v10 1/3] cfg80211: Simplify the handling of regulatory indoor setting Ilan Peer
2015-03-04  5:32 ` [PATCH v10 2/3] cfg80211: Add API to change the indoor regulatory setting Ilan Peer
2015-03-05 22:54   ` Luis R. Rodriguez [this message]
2015-03-04  5:32 ` [PATCH v10 3/3] cfg80211: Schedule timeout for all CRDA calls Ilan Peer
2015-03-05 22:55   ` Luis R. Rodriguez
2015-03-06  8:39     ` Johannes Berg
2015-03-08  7:34     ` Peer, Ilan

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=20150305225404.GB25035@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=arik@wizery.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).