linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: qca_merez <qca_merez@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	wil6210 <wil6210@qca.qualcomm.com>,
	qca_liord <qca_liord@qca.qualcomm.com>
Subject: Re: [PATCH v2 4/5] wil6210: add option to ignore OTA regulatory hints
Date: Fri, 19 May 2017 04:56:40 +0000	[thread overview]
Message-ID: <8737c1a1h6.fsf@qca.qualcomm.com> (raw)
In-Reply-To: 1494848759-3651-5-git-send-email-qca_merez@qca.qualcomm.com

Maya Erez <qca_merez@qca.qualcomm.com> writes:

> On some platforms, the regulatory domain (country) is set
> using mechanisms external to WIFI, such as cellular modem
> and GPS. In these scenarios the regulatory hints that
> are received over the air (in beacons and similar) can
> conflict and even cause an incorrect country to be set.
> Add an option to ignore the OTA regulatory hints to better
> support such scenarios.
>
> Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
> Signed-off-by: Maya Erez <qca_merez@qca.qualcomm.com>
> ---
>  drivers/net/wireless/ath/wil6210/cfg80211.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/drivers/net/wireless/ath/wil6210/cfg80211.c b/drivers/net/wi=
reless/ath/wil6210/cfg80211.c
> index 567fe43..0f297c0 100644
> --- a/drivers/net/wireless/ath/wil6210/cfg80211.c
> +++ b/drivers/net/wireless/ath/wil6210/cfg80211.c
> @@ -26,6 +26,11 @@
>  module_param(disable_ap_sme, bool, 0444);
>  MODULE_PARM_DESC(disable_ap_sme, " let user space handle AP mode SME");
> =20
> +static bool ignore_reg_hints;
> +module_param(ignore_reg_hints, bool, 0444);
> +MODULE_PARM_DESC(ignore_reg_hints,
> +		 " Ignore OTA regulatory hints (Default: false)");
> +
>  #define CHAN60G(_channel, _flags) {				\
>  	.band			=3D NL80211_BAND_60GHZ,		\
>  	.center_freq		=3D 56160 + (2160 * (_channel)),	\
> @@ -1763,6 +1768,11 @@ static void wil_wiphy_init(struct wiphy *wiphy)
> =20
>  	wiphy->n_vendor_commands =3D ARRAY_SIZE(wil_nl80211_vendor_commands);
>  	wiphy->vendor_commands =3D wil_nl80211_vendor_commands;
> +
> +	if (ignore_reg_hints) {
> +		wiphy->regulatory_flags |=3D REGULATORY_DISABLE_BEACON_HINTS;
> +		wiphy->regulatory_flags |=3D REGULATORY_COUNTRY_IE_IGNORE;
> +	}

I wonder should something like this be in cfg80211? Because I doubt
wil6210 is the only driver having this problem.

--=20
Kalle Valo=

  reply	other threads:[~2017-05-19  4:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 11:45 [PATCH v2 0/5] wil6210 patches Maya Erez
2017-05-15 11:45 ` [PATCH v2 1/5] wil6210: low level RF sector API Maya Erez
2017-05-23 15:31   ` [v2,1/5] " Kalle Valo
2017-05-15 11:45 ` [PATCH v2 2/5] wil6210: add option to load FTM FW Maya Erez
2017-05-15 11:45 ` [PATCH v2 3/5] wil6210: Improve AP stop handling Maya Erez
2017-05-15 11:45 ` [PATCH v2 4/5] wil6210: add option to ignore OTA regulatory hints Maya Erez
2017-05-19  4:56   ` Kalle Valo [this message]
2017-05-21 20:07     ` Maya Haim
2017-05-22 14:22       ` Kalle Valo
2017-05-15 11:45 ` [PATCH v2 5/5] wil6210: support devices with different PCIe bar size Maya Erez

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=8737c1a1h6.fsf@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=qca_liord@qca.qualcomm.com \
    --cc=qca_merez@qca.qualcomm.com \
    --cc=wil6210@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).