From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH v2 05/13] wiphy: use nl80211_parse_supported_frequencies
Date: Wed, 3 Aug 2022 14:36:36 -0700 [thread overview]
Message-ID: <20220803213644.277534-5-prestwoj@gmail.com> (raw)
In-Reply-To: <20220803213644.277534-1-prestwoj@gmail.com>
Removes the parser in wiphy and uses the helper instead
---
src/wiphy.c | 44 +++-----------------------------------------
1 file changed, 3 insertions(+), 41 deletions(-)
diff --git a/src/wiphy.c b/src/wiphy.c
index 4a778699..3a6cd48c 100644
--- a/src/wiphy.c
+++ b/src/wiphy.c
@@ -1190,42 +1190,6 @@ static void parse_supported_ciphers(struct wiphy *wiphy, const void *data,
}
}
-static void parse_supported_frequencies(struct wiphy *wiphy,
- struct l_genl_attr *freqs)
-{
- uint16_t type, len;
- const void *data;
- struct l_genl_attr attr;
-
- while (l_genl_attr_next(freqs, NULL, NULL, NULL)) {
- uint32_t freq = 0;
- bool disabled = false;
-
- if (!l_genl_attr_recurse(freqs, &attr))
- continue;
-
- while (l_genl_attr_next(&attr, &type, &len, &data)) {
-
- switch (type) {
- case NL80211_FREQUENCY_ATTR_FREQ:
- freq = *((uint32_t *) data);
- break;
- case NL80211_FREQUENCY_ATTR_DISABLED:
- disabled = true;
- break;
- }
- }
-
- if (!freq)
- continue;
-
- scan_freq_set_add(wiphy->supported_freqs, freq);
-
- if (disabled)
- scan_freq_set_add(wiphy->disabled_freqs, freq);
- }
-}
-
static int parse_supported_rates(struct l_genl_attr *attr, struct band *band)
{
uint16_t type;
@@ -1445,16 +1409,14 @@ static void parse_supported_bands(struct wiphy *wiphy,
band = *bandp;
-
while (l_genl_attr_next(&attr, &type, &len, &data)) {
struct l_genl_attr nested;
switch (type) {
case NL80211_BAND_ATTR_FREQS:
- if (!l_genl_attr_recurse(&attr, &nested))
- continue;
-
- parse_supported_frequencies(wiphy, &nested);
+ nl80211_parse_supported_frequencies(&attr,
+ wiphy->supported_freqs,
+ wiphy->disabled_freqs);
break;
case NL80211_BAND_ATTR_RATES:
--
2.34.3
next prev parent reply other threads:[~2022-08-03 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 21:36 [PATCH v2 01/13] wiphy: fix runtime error from bit shift James Prestwood
2022-08-03 21:36 ` [PATCH v2 02/13] scan: track scanned frequencies for entire request James Prestwood
2022-08-03 21:36 ` [PATCH v2 03/13] nl80211util: add nl80211_parse_supported_frequencies James Prestwood
2022-08-04 15:27 ` Denis Kenzior
2022-08-03 21:36 ` [PATCH v2 04/13] wiphy: track self-managed flag James Prestwood
2022-08-03 21:36 ` James Prestwood [this message]
2022-08-03 21:36 ` [PATCH v2 06/13] wiphy: add two regulatory domain state events James Prestwood
2022-08-04 15:31 ` Denis Kenzior
2022-08-03 21:36 ` [PATCH v2 07/13] wiphy: dump wiphy's on regulatory domain change James Prestwood
2022-08-03 21:36 ` [PATCH v2 08/13] wiphy: add wiphy_regdom_is_updating James Prestwood
2022-08-03 21:36 ` [PATCH v2 09/13] wiphy: add wiphy_country_is_unknown James Prestwood
2022-08-04 16:48 ` Denis Kenzior
2022-08-03 21:36 ` [PATCH v2 10/13] station: do full passive scan if 6GHz is supported but disabled James Prestwood
2022-08-03 21:36 ` [PATCH v2 11/13] scan: split full scans by band to enable 6GHz James Prestwood
2022-08-03 21:36 ` [PATCH v2 12/13] scan: watch for regdom updates " James Prestwood
2022-08-03 21:36 ` [PATCH v2 13/13] wiphy: don't re-dump wiphy if the regdom didn't change James Prestwood
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=20220803213644.277534-5-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