From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 02/10] nl80211util: parse additional channel restriction flags
Date: Tue, 20 Dec 2022 13:43:10 -0800 [thread overview]
Message-ID: <20221220214318.2041986-2-prestwoj@gmail.com> (raw)
In-Reply-To: <20221220214318.2041986-1-prestwoj@gmail.com>
---
src/band.h | 5 +++++
src/nl80211util.c | 15 +++++++++++++++
2 files changed, 20 insertions(+)
diff --git a/src/band.h b/src/band.h
index da4c0ae5..e196a416 100644
--- a/src/band.h
+++ b/src/band.h
@@ -59,6 +59,11 @@ struct band_freq_attrs {
bool supported : 1;
bool disabled : 1;
bool no_ir : 1;
+ bool no_ht40_plus : 1;
+ bool no_ht40_minus : 1;
+ bool no_80mhz : 1;
+ bool no_160mhz : 1;
+ bool no_he : 1;
} __attribute__ ((packed));
struct band {
diff --git a/src/nl80211util.c b/src/nl80211util.c
index 712cdec3..400871fd 100644
--- a/src/nl80211util.c
+++ b/src/nl80211util.c
@@ -533,6 +533,21 @@ int nl80211_parse_supported_frequencies(struct l_genl_attr *band_freqs,
case NL80211_FREQUENCY_ATTR_NO_IR:
freq_attr.no_ir = true;
break;
+ case NL80211_FREQUENCY_ATTR_NO_HT40_MINUS:
+ freq_attr.no_ht40_minus = true;
+ break;
+ case NL80211_FREQUENCY_ATTR_NO_HT40_PLUS:
+ freq_attr.no_ht40_plus = true;
+ break;
+ case NL80211_FREQUENCY_ATTR_NO_80MHZ:
+ freq_attr.no_80mhz = true;
+ break;
+ case NL80211_FREQUENCY_ATTR_NO_160MHZ:
+ freq_attr.no_160mhz = true;
+ break;
+ case NL80211_FREQUENCY_ATTR_NO_HE:
+ freq_attr.no_he = true;
+ break;
}
}
--
2.34.3
next prev parent reply other threads:[~2022-12-20 21:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 21:43 [PATCH 01/10] ap: make supported rates a common builder James Prestwood
2022-12-20 21:43 ` James Prestwood [this message]
2022-12-20 21:43 ` [PATCH 03/10] band: add ampdu_params value James Prestwood
2022-12-20 21:43 ` [PATCH 04/10] wiphy: add getter for HT capabilities James Prestwood
2022-12-27 17:22 ` Denis Kenzior
2022-12-20 21:43 ` [PATCH 05/10] band: add APIs to generate a chandef from frequency James Prestwood
2022-12-27 18:07 ` Denis Kenzior
2022-12-28 19:50 ` James Prestwood
2022-12-28 21:10 ` Denis Kenzior
2022-12-20 21:43 ` [PATCH 06/10] band: add band_chandef_width_to_string James Prestwood
2022-12-27 17:33 ` Denis Kenzior
2022-12-20 21:43 ` [PATCH 07/10] wiphy: add wiphy_supports_uapsd James Prestwood
2022-12-20 21:43 ` [PATCH 08/10] ap: include WMM parameter IE James Prestwood
2022-12-27 18:09 ` Denis Kenzior
2022-12-20 21:43 ` [PATCH 09/10] ap: build HT Capabilities/Operation elements James Prestwood
2022-12-20 21:43 ` [PATCH 10/10] ap: generate chandef for starting AP James Prestwood
2022-12-27 16:59 ` [PATCH 01/10] ap: make supported rates a common builder Denis Kenzior
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=20221220214318.2041986-2-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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