From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH] scan: remove early supported check for 6ghz in wiphy watch
Date: Mon, 12 Dec 2022 14:08:57 -0800 [thread overview]
Message-ID: <20221212220857.1284874-1-prestwoj@gmail.com> (raw)
If the regdom updates during a periodic scan the results will be
delayed until after the update in order to, potentially, add 6GHz
frequencies since they may become available. The delayed results
happen regardless of 6GHz support but scan_wiphy_watch() was
returning early if 6GHz was not supported causing the scan request
to never complete.
---
src/scan.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/src/scan.c b/src/scan.c
index 5d2f2957..f63b3ed2 100644
--- a/src/scan.c
+++ b/src/scan.c
@@ -1933,12 +1933,9 @@ static void scan_wiphy_watch(struct wiphy *wiphy,
struct scan_freq_set *freqs_6ghz;
struct scan_freq_set *allowed;
bool allow_6g;
- const struct scan_freq_set *supported =
- wiphy_get_supported_freqs(wiphy);
- /* Only care about regulatory events, and if 6GHz capable */
- if (event != WIPHY_STATE_WATCH_EVENT_REGDOM_DONE ||
- !(scan_freq_set_get_bands(supported) & BAND_FREQ_6_GHZ))
+ /* Only care about completed regulatory dumps */
+ if (event != WIPHY_STATE_WATCH_EVENT_REGDOM_DONE)
return;
if (!sc->sp.id)
--
2.34.3
next reply other threads:[~2022-12-12 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 22:08 James Prestwood [this message]
2022-12-13 20:19 ` [PATCH] scan: remove early supported check for 6ghz in wiphy watch 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=20221212220857.1284874-1-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;
as well as URLs for NNTP newsgroup(s).