linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: yhchuang@realtek.com
Cc: kvalo@codeaurora.org, Larry.Finger@lwfinger.net,
	pkshih@realtek.com, tehuang@realtek.com,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC v2 02/12] rtw88: core files
Date: Thu, 4 Oct 2018 13:42:35 +0200	[thread overview]
Message-ID: <20181004114235.GB16819@redhat.com> (raw)
In-Reply-To: <1538553748-26364-3-git-send-email-yhchuang@realtek.com>

On Wed, Oct 03, 2018 at 04:02:18PM +0800, yhchuang@realtek.com wrote:
> +static void rtw_restore_port_cfg(struct rtw_dev *rtwdev)
> +{
> +	struct rtw_vif *rtwvif;
> +	u32 config = ~0;
> +
> +	rcu_read_lock();
> +	list_for_each_entry(rtwvif, &rtwdev->vif_list, list)
list_for_each_entry_rcu

> +void rtw_lps_enter_check(struct rtw_dev *rtwdev)
> +{
> +	struct rtw_vif *rtwvif, *lps_if;
> +	u8 assoc_cnt = 0;
> +
> +	rcu_read_lock();
> +	list_for_each_entry(rtwvif, &rtwdev->vif_list, list) {
list_for_each_entry_rcu

> +static struct country_code_to_enum_rd all_countries[] = {
> +	{COUNTRY_CODE_FCC, "US"},
> +	{COUNTRY_CODE_IC, "US"},
> +	{COUNTRY_CODE_ETSI, "EC"},
> +	{COUNTRY_CODE_SPAIN, "EC"},
> +	{COUNTRY_CODE_FRANCE, "EC"},
> +	{COUNTRY_CODE_MKK, "JP"},
> +	{COUNTRY_CODE_MKK1, "JP"},
> +	{COUNTRY_CODE_ISRAEL, "EC"},
> +	{COUNTRY_CODE_TELEC, "JP"},
> +	{COUNTRY_CODE_MIC, "JP"},
> +	{COUNTRY_CODE_GLOBAL_DOMAIN, "JP"},
> +	{COUNTRY_CODE_WORLD_WIDE_13, "EC"},
> +	{COUNTRY_CODE_TELEC_NETGEAR, "EC"},
> +	{COUNTRY_CODE_WORLD_WIDE_13_5G_ALL, "US"},
> +};
> +
> +/* Only these channels allow active
> + * scan on all world regulatory domains
> + */
> +#define RTW_2GHZ_CH01_11	\
> +	REG_RULE(2412 - 10, 2462 + 10, 40, 0, 20, 0)
<snip>
> +static const
> +struct ieee80211_regdomain *rtw_regdomain_select(struct rtw_regulatory *reg)
> +{
> +	switch (reg->country_code) {
> +	case COUNTRY_CODE_FCC:
> +		return &rtw_regdom_no_midband;
> +	case COUNTRY_CODE_IC:
> +		return &rtw_regdom_11;
> +	case COUNTRY_CODE_TELEC_NETGEAR:
> +		return &rtw_regdom_60_64;
> +	case COUNTRY_CODE_ETSI:
> +	case COUNTRY_CODE_SPAIN:
> +	case COUNTRY_CODE_FRANCE:
> +	case COUNTRY_CODE_ISRAEL:
> +		return &rtw_regdom_12_13;
> +	case COUNTRY_CODE_MKK:
> +	case COUNTRY_CODE_MKK1:
> +	case COUNTRY_CODE_TELEC:
> +	case COUNTRY_CODE_MIC:
> +		return &rtw_regdom_14_60_64;
> +	case COUNTRY_CODE_GLOBAL_DOMAIN:
> +		return &rtw_regdom_14;
> +	case COUNTRY_CODE_WORLD_WIDE_13:
> +	case COUNTRY_CODE_WORLD_WIDE_13_5G_ALL:
> +		return &rtw_regdom_12_13_5g_all;
> +	default:
> +		return &rtw_regdom_no_midband;
> +	}

I'm not an expert on this, but I wonder if this is really needed
and standard linux regd stuff can not be used and regulatory
rules read from wireless-regd data-base.

Thanks
Stanislaw

  reply	other threads:[~2018-10-04 11:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03  8:02 [RFC v2 00/12] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips yhchuang
2018-10-03  8:02 ` [RFC v2 01/12] rtw88: main files yhchuang
2018-10-03  8:02 ` [RFC v2 02/12] rtw88: core files yhchuang
2018-10-04 11:42   ` Stanislaw Gruszka [this message]
2018-10-04 13:52     ` Stanislaw Gruszka
2018-10-08  8:22     ` Tony Chuang
2018-10-03  8:02 ` [RFC v2 03/12] rtw88: hci files yhchuang
2018-10-04 13:02   ` Stanislaw Gruszka
2018-10-04 13:25     ` Stanislaw Gruszka
2018-10-05 12:07     ` Tony Chuang
2018-10-06 12:29       ` Kalle Valo
2018-10-08  9:03         ` Tony Chuang
2018-10-08  9:34       ` Stanislaw Gruszka
2019-03-25 14:33         ` Brian Norris
2018-10-03  8:02 ` [RFC v2 04/12] rtw88: trx files yhchuang
2018-10-04 13:19   ` Stanislaw Gruszka
2018-10-05  9:20     ` Tony Chuang
2018-10-06 12:32       ` Kalle Valo
2018-10-08  9:19         ` Stanislaw Gruszka
2018-10-08  9:35           ` Tony Chuang
2018-10-08  9:25       ` Stanislaw Gruszka
2018-10-03  8:02 ` [RFC v2 05/12] rtw88: mac files yhchuang
2018-10-03  8:02 ` [RFC v2 06/12] rtw88: fw and efuse files yhchuang
2018-10-04 10:49   ` Stanislaw Gruszka
2018-10-05  9:19     ` Tony Chuang
2018-10-08  9:15       ` Stanislaw Gruszka
2018-10-06 12:34     ` Kalle Valo
2018-10-03  8:02 ` [RFC v2 07/12] rtw88: phy files yhchuang
2018-10-03  8:02 ` [RFC v2 08/12] rtw88: debug files yhchuang
2018-10-03  8:02 ` [RFC v2 09/12] rtw88: chip files yhchuang
2018-10-03  8:02 ` [RFC v2 10/12] rtw88: 8822B init table yhchuang
2018-10-03  8:02 ` [RFC v2 11/12] rtw88: 8822C " yhchuang
2018-10-03  8:02 ` [RFC v2 12/12] rtw88: Kconfig & Makefile yhchuang
2018-10-03 16:15 ` [RFC v2 00/12] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips Sid Hayn
2018-10-03 16:52   ` Larry Finger
2018-10-03 16:57     ` Sid Hayn
2018-10-03 17:38       ` Larry Finger

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=20181004114235.GB16819@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=tehuang@realtek.com \
    --cc=yhchuang@realtek.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).