From: Johannes Berg <johannes@sipsolutions.net>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>,
linux-wireless@vger.kernel.org
Cc: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>,
Dmitry Lebed <dlebed@quantenna.com>,
Dmitry Lebed <lebed.dmitry@gmail.com>
Subject: Re: [PATCH v2] cfg80211/nl80211: add DFS offload flag
Date: Fri, 23 Feb 2018 12:32:11 +0100 [thread overview]
Message-ID: <1519385531.2231.12.camel@sipsolutions.net> (raw)
In-Reply-To: <20180222091513.25456-1-sergey.matyukevich.os@quantenna.com>
On Thu, 2018-02-22 at 12:15 +0300, Sergey Matyukevich wrote:
> From: Dmitry Lebed <dlebed@quantenna.com>
>
> Add wiphy EXT_FEATURE flag to indicate that HW or driver does
> all DFS actions by itself.
> User-space functionality already implemented in hostapd using
> vendor-specific (QCA) OUI to advertise DFS offload support.
> Need to introduce generic flag to inform about DFS offload support.
> For deivces with DFS_OFFLOAD flag set user-space will no longer
> need to issue CAC or do any actions in response to
> "radar detected" events. HW will do everything by itself and send
> events to user-space to indicate that CAC was started/finished, etc.
>
> + * @NL80211_EXT_FEATURE_DFS_OFFLOAD: HW/driver will offload DFS actions.
> + * Device or driver will do all DFS-related actions by itself,
> + * informing user-space about CAC progress, radar detection event,
> + * channel change triggered by radar detection event.
> + * No need to start CAC from user-space, no need to react to
> + * "radar detected" event.
The "channel change" part bothers me a bit - isn't normally hostapd
very much in control of the channel? How does it even get notified of
the new channel? How can you configure the parameters like how many
beacons to include the (E)CSA IE for, and whether to add ECSA or not
etc?
johannes
next prev parent reply other threads:[~2018-02-23 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 9:15 [PATCH v2] cfg80211/nl80211: add DFS offload flag Sergey Matyukevich
2018-02-23 11:32 ` Johannes Berg [this message]
2018-02-23 16:23 ` Dmitry Lebed
2018-03-01 8:46 ` Sergey Matyukevich
2018-03-01 8:52 ` Johannes Berg
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=1519385531.2231.12.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=avinashp@quantenna.com \
--cc=dlebed@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=lebed.dmitry@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.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).