From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Marek Puzyniak <marek.puzyniak@tieto.com>
Cc: linux-wireless@vger.kernel.org,
Michal Kazior <michal.kazior@tieto.com>,
ath10k@lists.infradead.org
Subject: Re: [PATCH 2/3] ath10k: introduce DFS implementation
Date: Wed, 6 Nov 2013 11:54:32 +0200 [thread overview]
Message-ID: <877gclua7b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1383048394-15256-2-git-send-email-marek.puzyniak@tieto.com> (Marek Puzyniak's message of "Tue, 29 Oct 2013 13:06:33 +0100")
Marek Puzyniak <marek.puzyniak@tieto.com> writes:
> Configure interface combination for AP running on channels
> where radar detection is required. It allows only one type
> of interface - AP on DFS channel and limits number of AP
> interfaces to 8. Setup WMI channel flags accordingly to mac
> channel configuration. CAC based on additional monitor vdev
> is started if required for current channel.
>
> Signed-off-by: Marek Puzyniak <marek.puzyniak@tieto.com>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
[...]
> +static const struct ieee80211_iface_limit ath10k_if_dfs_limits[] = {
> + {
> + .max = 8,
> + .types = BIT(NL80211_IFTYPE_AP)
> + },
> +};
> +
> +static const struct ieee80211_iface_combination ath10k_if_comb[] = {
> + {
> + .limits = ath10k_if_limits,
> + .n_limits = ARRAY_SIZE(ath10k_if_limits),
> + .max_interfaces = 8,
> + .num_different_channels = 1,
> + .beacon_int_infra_match = true,
> + },
> + {
> + .limits = ath10k_if_dfs_limits,
> + .n_limits = ARRAY_SIZE(ath10k_if_dfs_limits),
> + .max_interfaces = 8,
> + .num_different_channels = 1,
> + .beacon_int_infra_match = true,
> + .radar_detect_widths = BIT(NL80211_CHAN_WIDTH_20_NOHT) |
> + BIT(NL80211_CHAN_WIDTH_20) |
> + BIT(NL80211_CHAN_WIDTH_40) |
> + BIT(NL80211_CHAN_WIDTH_80),
> + }
> };
>
> static struct ieee80211_sta_vht_cap ath10k_create_vht_cap(struct ath10k *ar)
> @@ -3531,8 +3667,8 @@ int ath10k_mac_register(struct ath10k *ar)
> */
> ar->hw->queues = 4;
>
> - ar->hw->wiphy->iface_combinations = &ath10k_if_comb;
> - ar->hw->wiphy->n_iface_combinations = 1;
> + ar->hw->wiphy->iface_combinations = ath10k_if_comb;
> + ar->hw->wiphy->n_iface_combinations = ARRAY_SIZE(ath10k_if_comb);
If ATH10K_DFS_CERTIFIED is disabled should we still enable
radar_detect_widths? Doesn't that enable DFS even it should be disabled?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2013-11-06 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 12:06 [PATCH 1/3] ath10k: add phyerr/dfs handling Marek Puzyniak
2013-10-29 12:06 ` [PATCH 2/3] ath10k: introduce DFS implementation Marek Puzyniak
2013-11-06 9:54 ` Kalle Valo [this message]
2013-10-29 12:06 ` [PATCH 3/3] ath10k: add debugfs file to control radar events blocking Marek Puzyniak
2013-10-29 17:25 ` [PATCH 1/3] ath10k: add phyerr/dfs handling Joe Perches
2013-11-06 9:47 ` Kalle Valo
2013-11-06 13:52 ` Janusz Dziedzic
2013-11-08 13:41 ` Kalle Valo
2013-11-13 8:59 ` Kalle Valo
2013-11-06 9:55 ` Kalle Valo
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=877gclua7b.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marek.puzyniak@tieto.com \
--cc=michal.kazior@tieto.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