From: Wen Gong <wgong@codeaurora.org>
To: Thomas Pedersen <thomas@adapt-ip.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v4 14/17] mac80211: support S1G association
Date: Mon, 23 Nov 2020 16:38:23 +0800 [thread overview]
Message-ID: <af51dd8e9dea2961546a502d9090d1a7@codeaurora.org> (raw)
In-Reply-To: <20200922022818.15855-15-thomas@adapt-ip.com>
On 2020-09-22 10:28, Thomas Pedersen wrote:
...
> @@ -3446,6 +3453,42 @@ bool ieee80211_chandef_he_6ghz_oper(struct
> ieee80211_sub_if_data *sdata,
>
> *chandef = he_chandef;
>
> + return false;
> +}
This change the "return true" to "return false" by default of
ieee80211_chandef_he_6ghz_oper.
It should be typo mistake.
> +
> +bool ieee80211_chandef_s1g_oper(const struct ieee80211_s1g_oper_ie
> *oper,
> + struct cfg80211_chan_def *chandef)
> +{
> + u32 oper_freq;
> +
> + if (!oper)
> + return false;
> +
> + switch (FIELD_GET(S1G_OPER_CH_WIDTH_OPER, oper->ch_width)) {
> + case IEEE80211_S1G_CHANWIDTH_1MHZ:
> + chandef->width = NL80211_CHAN_WIDTH_1;
> + break;
> + case IEEE80211_S1G_CHANWIDTH_2MHZ:
> + chandef->width = NL80211_CHAN_WIDTH_2;
> + break;
> + case IEEE80211_S1G_CHANWIDTH_4MHZ:
> + chandef->width = NL80211_CHAN_WIDTH_4;
> + break;
> + case IEEE80211_S1G_CHANWIDTH_8MHZ:
> + chandef->width = NL80211_CHAN_WIDTH_8;
> + break;
> + case IEEE80211_S1G_CHANWIDTH_16MHZ:
> + chandef->width = NL80211_CHAN_WIDTH_16;
> + break;
> + default:
> + return false;
> + }
> +
> + oper_freq = ieee80211_channel_to_freq_khz(oper->oper_ch,
> + NL80211_BAND_S1GHZ);
> + chandef->center_freq1 = KHZ_TO_MHZ(oper_freq);
> + chandef->freq1_offset = oper_freq % 1000;
> +
> return true;
> }
>
....
next prev parent reply other threads:[~2020-11-23 8:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 2:28 [PATCH v4 00/17] add support for S1G association Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 01/17] {cfg,mac}80211: get correct default channel width for S1G Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 02/17] mac80211: s1g: choose scanning width based on frequency Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 03/17] nl80211: support S1G capabilities Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 04/17] mac80211: support S1G STA capabilities Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 05/17] cfg80211: convert S1G beacon to scan results Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 06/17] cfg80211: parse S1G Operation element for BSS channel Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 07/17] mac80211: convert S1G beacon to scan results Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 08/17] cfg80211: handle Association Response from S1G STA Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 09/17] mac80211: encode listen interval for S1G Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 10/17] mac80211: don't calculate duration " Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 11/17] mac80211: handle S1G low rates Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 12/17] mac80211: avoid rate init for S1G band Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 13/17] mac80211: receive and process S1G beacons Thomas Pedersen
2020-12-08 7:44 ` Wen Gong
2020-12-08 18:19 ` Thomas Pedersen
2020-12-09 2:48 ` Wen Gong
2020-09-22 2:28 ` [PATCH v4 14/17] mac80211: support S1G association Thomas Pedersen
2020-09-28 12:17 ` Johannes Berg
2020-09-29 17:07 ` Thomas Pedersen
2020-11-23 8:38 ` Wen Gong [this message]
2020-11-23 8:39 ` Wen Gong
2020-11-23 18:40 ` Thomas Pedersen
2020-11-24 3:59 ` Wen Gong
2020-11-24 7:04 ` Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 15/17] nl80211: include frequency offset in survey info Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 16/17] mac80211_hwsim: fix TSF timestamp write to S1G beacon Thomas Pedersen
2020-09-22 2:28 ` [PATCH v4 17/17] mac80211_hwsim: indicate support for S1G Thomas Pedersen
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=af51dd8e9dea2961546a502d9090d1a7@codeaurora.org \
--to=wgong@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@adapt-ip.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).