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: [PATCH V3 1/8] nl80211: add 6GHz band definition to enum nl80211_band
Date: Fri, 2 Aug 2019 13:30:58 +0200 [thread overview]
Message-ID: <1564745465-21234-2-git-send-email-arend.vanspriel@broadcom.com> (raw)
In-Reply-To: <1564745465-21234-1-git-send-email-arend.vanspriel@broadcom.com>
In the 802.11ax specification a new band is introduced, which
is also proposed by FCC for unlicensed use. This band is referred
to as 6GHz spanning frequency range from 5925 to 7125 MHz.
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>
---
changes:
- V2
fix ABI breakage by appending the new band definition.
- V3
fix warning (-Wswitch) in mac80211.
---
include/uapi/linux/nl80211.h | 2 ++
net/mac80211/tx.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h
index 822851d..4d5988f 100644
--- a/include/uapi/linux/nl80211.h
+++ b/include/uapi/linux/nl80211.h
@@ -4543,6 +4543,7 @@ enum nl80211_txrate_gi {
* @NL80211_BAND_2GHZ: 2.4 GHz ISM band
* @NL80211_BAND_5GHZ: around 5 GHz band (4.9 - 5.7 GHz)
* @NL80211_BAND_60GHZ: around 60 GHz band (58.32 - 69.12 GHz)
+ * @NL80211_BAND_6GHZ: around 6 GHz band (5.9 - 7.2 GHz)
* @NUM_NL80211_BANDS: number of bands, avoid using this in userspace
* since newer kernel versions may support more bands
*/
@@ -4550,6 +4551,7 @@ enum nl80211_band {
NL80211_BAND_2GHZ,
NL80211_BAND_5GHZ,
NL80211_BAND_60GHZ,
+ NL80211_BAND_6GHZ,
NUM_NL80211_BANDS,
};
diff --git a/net/mac80211/tx.c b/net/mac80211/tx.c
index 235c637..1fa4227 100644
--- a/net/mac80211/tx.c
+++ b/net/mac80211/tx.c
@@ -162,6 +162,7 @@ static __le16 ieee80211_duration(struct ieee80211_tx_data *tx,
break;
}
case NL80211_BAND_5GHZ:
+ case NL80211_BAND_6GHZ:
if (r->flags & IEEE80211_RATE_MANDATORY_A)
mrate = r->bitrate;
break;
--
1.9.1
next prev parent reply other threads:[~2019-08-02 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 11:30 [PATCH V3 0/8] nl80211: add 6GHz band support Arend van Spriel
2019-08-02 11:30 ` Arend van Spriel [this message]
2019-08-02 11:30 ` [PATCH V3 2/8] cfg80211: add 6GHz UNII band definitions Arend van Spriel
2019-08-02 11:31 ` [PATCH V3 3/8] cfg80211: util: add 6GHz channel to freq conversion and vice versa Arend van Spriel
2019-08-02 11:31 ` [PATCH V3 4/8] cfg80211: extend ieee80211_operating_class_to_band() for 6GHz Arend van Spriel
2019-08-02 11:31 ` [PATCH V3 5/8] cfg80211: add 6GHz in code handling array with NUM_NL80211_BANDS entries Arend van Spriel
2019-08-02 11:31 ` [PATCH V3 6/8] cfg80211: use same IR permissive rules for 6GHz band Arend van Spriel
2019-08-02 11:31 ` [PATCH V3 7/8] cfg80211: ibss: use 11a mandatory rates for 6GHz band operation Arend van Spriel
2019-08-02 11:31 ` [PATCH V3 8/8] cfg80211: apply same mandatory rate flags for 5GHz and 6GHz Arend van Spriel
[not found] ` <eddfd4e1abbd1dc57858fff61ee2523b@codeaurora.org>
2019-09-21 18:49 ` [PATCH V3 0/8] nl80211: add 6GHz band support Arend Van Spriel
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=1564745465-21234-2-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