Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Jérôme Pouiller" <jerome.pouiller@silabs.com>
Subject: [PATCH v3 0/8] wfx: implement Remain On Channel
Date: Wed,  4 Oct 2023 19:28:35 +0200	[thread overview]
Message-ID: <20231004172843.195332-1-jerome.pouiller@silabs.com> (raw)

Hello,

Apart from the 3 first patch, this series implements Remain On Channel for
WF200 chips. The implementation is a bit twisted (I hijack the scan feature
to implements RoC). However, it has been extensively tested with
DPP/EasyConnect and I have not noticed any issue.

v3:
  - Patch 5 and 6 has been squashed.
  - Reordered patches 5 to 9. It was not so easy, but I guarantee the final
    code is the same and every patch compile.
v2:
  - Rebase on last stable tree

Jérôme Pouiller (8):
  wifi: wfx: fix power_save setting when AP is stopped
  wifi: wfx: relocate wfx_rate_mask_to_hw()
  wifi: wfx: move wfx_skb_*() out of the header file
  wifi: wfx: introduce hif_scan_uniq()
  wifi: wfx: simplify exclusion between scan and Rx filters
  wifi: wfx: scan_lock is global to the device
  wifi: wfx: allow to send frames during ROC
  wifi: wfx: implement wfx_remain_on_channel()

 drivers/net/wireless/silabs/wfx/data_tx.c | 54 ++++++++++++++++---
 drivers/net/wireless/silabs/wfx/data_tx.h | 21 ++------
 drivers/net/wireless/silabs/wfx/hif_tx.c  | 43 +++++++++++++++
 drivers/net/wireless/silabs/wfx/hif_tx.h  |  1 +
 drivers/net/wireless/silabs/wfx/main.c    |  5 ++
 drivers/net/wireless/silabs/wfx/queue.c   | 38 ++++++++++---
 drivers/net/wireless/silabs/wfx/queue.h   |  1 +
 drivers/net/wireless/silabs/wfx/scan.c    | 66 ++++++++++++++++++++++-
 drivers/net/wireless/silabs/wfx/scan.h    |  6 +++
 drivers/net/wireless/silabs/wfx/sta.c     | 41 +++++---------
 drivers/net/wireless/silabs/wfx/sta.h     |  1 -
 drivers/net/wireless/silabs/wfx/wfx.h     |  8 +--
 12 files changed, 218 insertions(+), 67 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-10-04 17:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 17:28 Jérôme Pouiller [this message]
2023-10-04 17:28 ` [PATCH v3 1/8] wifi: wfx: fix power_save setting when AP is stopped Jérôme Pouiller
2023-10-09  6:53   ` Kalle Valo
2023-10-04 17:28 ` [PATCH v3 2/8] wifi: wfx: relocate wfx_rate_mask_to_hw() Jérôme Pouiller
2023-10-04 17:28 ` [PATCH v3 3/8] wifi: wfx: move wfx_skb_*() out of the header file Jérôme Pouiller
2023-10-04 17:28 ` [PATCH v3 4/8] wifi: wfx: introduce hif_scan_uniq() Jérôme Pouiller
2023-10-04 17:28 ` [PATCH v3 5/8] wifi: wfx: simplify exclusion between scan and Rx filters Jérôme Pouiller
2023-10-04 17:28 ` [PATCH v3 6/8] wifi: wfx: scan_lock is global to the device Jérôme Pouiller
2023-10-04 17:28 ` [PATCH v3 7/8] wifi: wfx: allow to send frames during ROC Jérôme Pouiller
2024-11-26  7:27   ` Sverdlin, Alexander
2024-11-26 14:45     ` Jérôme Pouiller
2024-11-26 15:41       ` Sverdlin, Alexander
2024-11-26 15:54       ` Sverdlin, Alexander
2024-11-27  9:18         ` Jérôme Pouiller
2023-10-04 17:28 ` [PATCH v3 8/8] wifi: wfx: implement wfx_remain_on_channel() Jérôme Pouiller

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=20231004172843.195332-1-jerome.pouiller@silabs.com \
    --to=jerome.pouiller@silabs.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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