From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: [RFC 7/8] cfg80211: ibss: use 11a mandatory rates for 6GHz band operation
Date: Mon, 20 May 2019 14:00:44 +0200 [thread overview]
Message-ID: <1558353645-18119-8-git-send-email-arend.vanspriel@broadcom.com> (raw)
In-Reply-To: <1558353645-18119-1-git-send-email-arend.vanspriel@broadcom.com>
The default mandatory rates, ie. when not specified by user-space, is
determined by the band. Select 11a rateset for 6GHz band.
Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
Reviewed-by: Leon Zegers <leon.zegers@broadcom.com>
Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
---
net/wireless/ibss.c | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/net/wireless/ibss.c b/net/wireless/ibss.c
index d1743e6..ae8fe66 100644
--- a/net/wireless/ibss.c
+++ b/net/wireless/ibss.c
@@ -104,13 +104,19 @@ int __cfg80211_join_ibss(struct cfg80211_registered_device *rdev,
* use the mandatory rate set for 11b or
* 11a for maximum compatibility.
*/
- struct ieee80211_supported_band *sband =
- rdev->wiphy.bands[params->chandef.chan->band];
+ struct ieee80211_supported_band *sband;
+ enum nl80211_band band;
+ u32 flag;
int j;
- u32 flag = params->chandef.chan->band == NL80211_BAND_5GHZ ?
- IEEE80211_RATE_MANDATORY_A :
- IEEE80211_RATE_MANDATORY_B;
+ band = params->chandef.chan->band;
+ if (band == NL80211_BAND_5GHZ ||
+ band == NL80211_BAND_6GHZ)
+ flag = IEEE80211_RATE_MANDATORY_A;
+ else
+ flag = IEEE80211_RATE_MANDATORY_B;
+
+ sband = rdev->wiphy.bands[band];
for (j = 0; j < sband->n_bitrates; j++) {
if (sband->bitrates[j].flags & flag)
params->basic_rates |= BIT(j);
--
1.9.1
next prev parent reply other threads:[~2019-05-20 12:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 12:00 [RFC 0/8] nl80211: add 6GHz band support Arend van Spriel
2019-05-20 12:00 ` [RFC 1/8] nl80211: add 6GHz band definition to enum nl80211_band Arend van Spriel
2019-05-30 14:53 ` Jeff Johnson
2019-05-30 16:07 ` Arend Van Spriel
2019-05-30 17:43 ` Jeff Johnson
2019-05-30 17:52 ` Arend Van Spriel
2019-05-20 12:00 ` [RFC 2/8] cfg80211: add 6GHz UNII band definitions Arend van Spriel
2019-05-20 12:00 ` [RFC 3/8] cfg80211: util: add 6GHz channel to freq conversion and vice versa Arend van Spriel
2019-05-20 12:00 ` [RFC 4/8] cfg80211: extend ieee80211_operating_class_to_band() for 6GHz Arend van Spriel
2019-05-20 12:00 ` [RFC 5/8] cfg80211: add 6GHz in code handling array with NUM_NL80211_BANDS entries Arend van Spriel
2019-05-20 12:00 ` [RFC 6/8] cfg80211: use same IR permissive rules for 6GHz band Arend van Spriel
2019-05-20 12:00 ` Arend van Spriel [this message]
2019-05-20 12:00 ` [RFC 8/8] cfg80211: apply same mandatory rate flags for 5GHz and 6GHz Arend van Spriel
2019-05-24 11:56 ` [RFC 0/8] nl80211: add 6GHz band support Johannes Berg
2019-05-24 18:38 ` Arend Van Spriel
2019-05-27 20:46 ` Arend Van Spriel
2019-06-03 10:39 ` Arend Van Spriel
2019-06-21 19:41 ` Arend Van Spriel
2019-06-28 13:04 ` Johannes Berg
2019-07-11 11:30 ` Arend Van Spriel
2019-07-12 9:30 ` Johannes Berg
2019-07-12 10:40 ` Arend Van Spriel
2019-07-12 15:16 ` Igor Mitsyanko
2019-07-12 20:06 ` Johannes Berg
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=1558353645-18119-8-git-send-email-arend.vanspriel@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--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).