From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Veerendranath Jakkam <quic_vjakkam@quicinc.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: Add support to configure allowed frequency list for AP operation
Date: Thu, 30 Mar 2023 19:30:21 +0300 [thread overview]
Message-ID: <ZCW5HVMLHHW2bzKW@w1.fi> (raw)
In-Reply-To: <421e93d78deda5ac9e62c58ee275758a3355a503.camel@sipsolutions.net>
On Tue, Mar 28, 2023 at 11:42:17AM +0200, Johannes Berg wrote:
> On Tue, 2023-03-28 at 15:01 +0530, Veerendranath Jakkam wrote:
> > Add support to configure the list of allowed 20 MHz channels for AP
> > operation using an array of channel center frequencies in MHz, this
> > configuration is valid until the AP is stopped. Driver shall filter out
> > channels on top of this list of channels based on regulatory or other
> > constraints during channel switch etc. Driver shall stop the AP
> > operation if all the channels are filtered out during such operation.
>
> Normally hostapd is doing anything related to the channel picking, so
> you need to explain why this is needed.
hostapd does this for many cases, but there are drivers, including a
couple of the upstream drivers, that select a channel internally for
channel switch cases. Those would be able to use this information. Is
that of sufficient generic interest or do you prefer vendor commands to
be used for such functionality?
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2023-03-30 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 9:31 [PATCH] nl80211: Add support to configure allowed frequency list for AP operation Veerendranath Jakkam
2023-03-28 9:42 ` Johannes Berg
2023-03-30 16:30 ` Jouni Malinen [this message]
2023-03-31 9:14 ` Johannes Berg
2023-03-31 9:34 ` Jouni Malinen
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=ZCW5HVMLHHW2bzKW@w1.fi \
--to=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_vjakkam@quicinc.com \
/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).