From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 02/10] cfg80211: validate 6 GHz chandef
Date: Wed, 29 Apr 2020 17:02:24 -0700 [thread overview]
Message-ID: <f7fa5618844630a3315acad53765e5e5@codeaurora.org> (raw)
In-Reply-To: <73a4e63e16bffb69cd9b62fd904b926dd5278fbf.camel@sipsolutions.net>
On 2020-04-29 07:26, Johannes Berg wrote:
> On Fri, 2020-04-24 at 15:41 -0700, Rajkumar Manoharan wrote:
>>
>> +static inline bool
>> +cfg80211_chandef_is_6ghz(const struct cfg80211_chan_def *chandef)
>> +{
>> + return (chandef->center_freq1 > 5940 && chandef->center_freq1 <
>> 7105);
>> +}
>
> Seems like this
>
>> +++ b/net/wireless/chan.c
>> @@ -19,6 +19,29 @@ static bool cfg80211_valid_60g_freq(u32 freq)
>> return freq >= 58320 && freq <= 70200;
>> }
>>
>> +static bool cfg80211_is_6ghz_freq(u32 freq)
>> +{
>> + return (freq > 5940 && freq < 7105);
>> +}
>
> should use this, by also exposing it, or something.
>
Sure. Export this and remove the above one.
>> +static enum nl80211_chan_width cfg80211_chan_to_bw_6ghz(u8 idx)
>> +{
>> + /* channels: 1, 5, 9, 13... */
>> + if ((idx & 0x3) == 0x1)
>> + return NL80211_CHAN_WIDTH_20;
>> + /* channels 3, 11, 19... */
>> + if ((idx & 0x7) == 0x3)
>> + return NL80211_CHAN_WIDTH_40;
>> + /* channels 7, 23, 39.. */
>> + if ((idx & 0xf) == 0x7)
>> + return NL80211_CHAN_WIDTH_80;
>> + /* channels 15, 47, 79...*/
>> + if ((idx & 0x1f) == 0xf)
>> + return NL80211_CHAN_WIDTH_160;
>> +
>> + return NL80211_CHAN_WIDTH_20;
>> +}
>
> We haven't really done that for anything else - is that really
> necessary?
>
Hmm.. to check whether give center_freq1 chan_idx is allowed to operate
in given bandwidth.
Similar to center_idx_to_bw_6ghz of hostapd, this API is used to chandef
bw.
[...]
>> @@ -213,6 +255,10 @@ bool cfg80211_chandef_valid(const struct
>> cfg80211_chan_def *chandef)
>> !cfg80211_edmg_chandef_valid(chandef))
>> return false;
>>
>> + if (cfg80211_chandef_is_6ghz(chandef) &&
>> + !cfg80211_6ghz_chandef_valid(chandef))
>> + return false;
>
> You only get there if it was in range ...
>
> Not sure about this whole patch, it seems a bit pointless?
>
Don't we have to check chandef bw? If not, I will drop the change.
-Rajkumar
next prev parent reply other threads:[~2020-04-30 0:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 22:41 [PATCH 00/10] mac80211: add 6 GHz IEs support Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 01/10] mac80211: fix memory overlap due to variable length param Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 02/10] cfg80211: validate 6 GHz chandef Rajkumar Manoharan
2020-04-29 14:26 ` Johannes Berg
2020-04-30 0:02 ` Rajkumar Manoharan [this message]
2020-04-30 19:54 ` Johannes Berg
2020-04-24 22:41 ` [PATCH 03/10] nl80211: add HE 6 GHz Band Capability support Rajkumar Manoharan
2020-04-29 14:28 ` Johannes Berg
2020-04-30 0:04 ` Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 04/10] mac80211: add HE 6 GHz Band Capabilities into parse extension Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 05/10] mac80211: handle HE 6 GHz Capability in HE STA processing Rajkumar Manoharan
2020-04-29 14:31 ` Johannes Berg
2020-04-30 0:11 ` Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 06/10] mac80211: add HE 6 GHz Band Capability IE in assoc. request Rajkumar Manoharan
2020-04-29 14:33 ` Johannes Berg
2020-04-30 0:14 ` Rajkumar Manoharan
2020-04-30 19:52 ` Johannes Berg
2020-04-24 22:41 ` [PATCH 07/10] mac80211: build HE operation with 6 GHz oper information Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 08/10] mac80211: do not allow HT/VHT IEs in 6 GHz mesh mode Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 09/10] mac80211: determine chantype from HE operation in 6 GHz Rajkumar Manoharan
2020-04-29 14:34 ` Johannes Berg
2020-04-30 0:18 ` Rajkumar Manoharan
2020-04-30 19:53 ` Johannes Berg
2020-04-24 22:41 ` [PATCH 10/10] ath11k: build HE 6 GHz capability Rajkumar Manoharan
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=f7fa5618844630a3315acad53765e5e5@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=johannes@sipsolutions.net \
--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).