Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: "kvalo@kernel.org" <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Bernie Huang" <phhuang@realtek.com>
Subject: Re: [PATCH v2 0/5] wifi: rtw89: preparation of multiple interface concurrency support
Date: Thu, 16 Mar 2023 12:20:40 +0000	[thread overview]
Message-ID: <9bdda86cb36feb948ecdc10acf7346e3cee2ae1f.camel@realtek.com> (raw)
In-Reply-To: <20230316121206.11479-1-pkshih@realtek.com>

On Thu, 2023-03-16 at 20:12 +0800, Ping-Ke Shih wrote:
> To support concurrency, we implement beacon filter, CQM and
> ieee80211::remain_on_channel ops. Since our firmware doesn't support to TX
> null packet while doing remain-on-channel, driver does this instead. To
> ensure null packet send out before switching channel, patch 2/5 adds a
> waiting mechanism.
> 
> The patches 4/5 and 5/5 refine things we found during developing.
> 
> v2:
>   - patch 1/5
>     - remove unnecessary type casting
>     - use clear style of mask definition for H2C/C2H
>   - patch 2/5
>     - add comment to describe why polling can help freeing
>   - others
>     - no change
> 
> Po-Hao Huang (5):
>   wifi: rtw89: 8852c: add beacon filter and CQM support
>   wifi: rtw89: add function to wait for completion of TX skbs
>   wifi: rtw89: add ieee80211::remain_on_channel ops
>   wifi: rtw89: add flag check for power state
>   wifi: rtw89: fix authentication fail during scan
> 
>  drivers/net/wireless/realtek/rtw89/chan.c     |  35 +++
>  drivers/net/wireless/realtek/rtw89/chan.h     |   3 +
>  drivers/net/wireless/realtek/rtw89/core.c     | 288 +++++++++++++++++-
>  drivers/net/wireless/realtek/rtw89/core.h     |  64 ++++
>  drivers/net/wireless/realtek/rtw89/fw.c       | 118 ++++++-
>  drivers/net/wireless/realtek/rtw89/fw.h       |  48 +++
>  drivers/net/wireless/realtek/rtw89/mac.c      |  61 ++++
>  drivers/net/wireless/realtek/rtw89/mac.h      |   1 +
>  drivers/net/wireless/realtek/rtw89/mac80211.c |  88 +++++-
>  drivers/net/wireless/realtek/rtw89/pci.c      |   6 +
>  drivers/net/wireless/realtek/rtw89/pci.h      |   4 +-
>  drivers/net/wireless/realtek/rtw89/ps.c       |   6 +
>  drivers/net/wireless/realtek/rtw89/ps.h       |  16 +
>  13 files changed, 723 insertions(+), 15 deletions(-)
> 

I messed up v2. Please ignore.
Sorry for that.

Ping-Ke



      parent reply	other threads:[~2023-03-16 12:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 12:12 [PATCH v2 0/5] wifi: rtw89: preparation of multiple interface concurrency support Ping-Ke Shih
2023-03-16 12:12 ` [PATCH v2 1/5] wifi: rtw89: 8852c: add beacon filter and CQM support Ping-Ke Shih
2023-03-16 12:12 ` [PATCH v2 2/5] wifi: rtw89: add function to wait for completion of TX skbs Ping-Ke Shih
2023-03-16 12:12 ` [PATCH v2 2/5] wifi: rtw89: add function to wait for completion of tx skbs Ping-Ke Shih
2023-03-16 12:12 ` [PATCH v2 3/5] wifi: rtw89: add ieee80211::remain_on_channel ops Ping-Ke Shih
2023-03-16 12:12 ` [PATCH v2 4/5] wifi: rtw89: add flag check for power state Ping-Ke Shih
2023-03-16 12:12 ` [PATCH v2 5/5] wifi: rtw89: fix authentication fail during scan Ping-Ke Shih
2023-03-16 12:20 ` Ping-Ke Shih [this message]

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=9bdda86cb36feb948ecdc10acf7346e3cee2ae1f.camel@realtek.com \
    --to=pkshih@realtek.com \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=phhuang@realtek.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