linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: nbd@nbd.name, johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, lorenzo.bianconi@redhat.com,
	ryder.lee@mediatek.com, evelyn.tsai@mediatek.com,
	john@phrozen.org
Subject: [RFC 0/7] add offchannel monitor chain support
Date: Tue, 28 Sep 2021 17:14:31 +0200	[thread overview]
Message-ID: <cover.1632841652.git.lorenzo@kernel.org> (raw)

Introduce the capability to configure a dedicated chain available for radar
detection on some hw (e.g. mt7915). The driver is supposed to implement CAC
management in sw or fw while hostapd (or iw) will implement the logic to
select and configure the monitored channel.
Using a dedicated chain to perform the CAC, the AP can avoid the CAC downtime
switching to a new DFS channel.

Lorenzo Bianconi (7):
  mac80211: introduce set_offchan_chain callback
  cfg80211: introduce nl80211_set_offchan_chain callback
  cfg80211: introduce cfg80211_cac_offchan_event routine
  mt76: mt7915: introduce mt7915_set_offchan_chain routine
  mt76: mt7915: enable radar trigger on rdd2
  mt76: mt7915: introduce rdd_monitor debugfs node
  mt76: mt7915: add cac support for offchannel chain

 .../wireless/mediatek/mt76/mt7915/debugfs.c   | 37 +++++++++-
 .../net/wireless/mediatek/mt76/mt7915/init.c  |  4 ++
 .../net/wireless/mediatek/mt76/mt7915/mac.c   | 57 ++++++++++++++++
 .../net/wireless/mediatek/mt76/mt7915/main.c  | 33 +++++++++
 .../net/wireless/mediatek/mt76/mt7915/mcu.c   | 67 ++++++++++++++++++-
 .../net/wireless/mediatek/mt76/mt7915/mcu.h   | 24 +++++++
 .../wireless/mediatek/mt76/mt7915/mt7915.h    | 10 +++
 include/net/cfg80211.h                        | 19 ++++++
 include/net/mac80211.h                        |  5 ++
 include/uapi/linux/nl80211.h                  |  6 ++
 net/mac80211/cfg.c                            | 13 ++++
 net/wireless/mlme.c                           | 26 +++++++
 net/wireless/nl80211.c                        | 41 ++++++++++++
 net/wireless/rdev-ops.h                       | 17 +++++
 net/wireless/trace.h                          | 19 ++++++
 15 files changed, 375 insertions(+), 3 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-09-28 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 15:14 Lorenzo Bianconi [this message]
2021-09-28 15:14 ` [RFC 1/7] mac80211: introduce set_offchan_chain callback Lorenzo Bianconi
2021-09-28 15:14 ` [RFC 2/7] cfg80211: introduce nl80211_set_offchan_chain callback Lorenzo Bianconi
2021-09-28 15:14 ` [RFC 3/7] cfg80211: introduce cfg80211_cac_offchan_event routine Lorenzo Bianconi
2021-09-28 15:14 ` [RFC 4/7] mt76: mt7915: introduce mt7915_set_offchan_chain routine Lorenzo Bianconi
2021-09-28 15:14 ` [RFC 5/7] mt76: mt7915: enable radar trigger on rdd2 Lorenzo Bianconi
2021-09-28 15:14 ` [RFC 6/7] mt76: mt7915: introduce rdd_monitor debugfs node Lorenzo Bianconi
2021-09-28 15:14 ` [RFC 7/7] mt76: mt7915: add cac support for offchannel chain Lorenzo Bianconi

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=cover.1632841652.git.lorenzo@kernel.org \
    --to=lorenzo@kernel.org \
    --cc=evelyn.tsai@mediatek.com \
    --cc=johannes@sipsolutions.net \
    --cc=john@phrozen.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=nbd@nbd.name \
    --cc=ryder.lee@mediatek.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).