From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <tony0620emma@gmail.com>, <phhuang@realtek.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 4/7] wifi: rtw88: disallow scan and PS during AP mode
Date: Wed, 12 Apr 2023 15:39:44 +0300 [thread overview]
Message-ID: <877cuh8eb3.fsf@kernel.org> (raw)
In-Reply-To: <20230401124410.33221-5-pkshih@realtek.com> (Ping-Ke Shih's message of "Sat, 1 Apr 2023 20:44:07 +0800")
Ping-Ke Shih <pkshih@realtek.com> writes:
> From: Po-Hao Huang <phhuang@realtek.com>
>
> During concurrent operation, the VIF sharing same channel with AP mode
> might scan. Reject those scan requests from driver when there's AP
> currently operating. Also, disallow entering power saving mode.
>
> Signed-off-by: Po-Hao Huang <phhuang@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
How is a station interface useful if it cannot scan at all? IMHO quite
hard limitation.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-04-12 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 12:44 [PATCH 0/7] wifi: rtw88: support single channel concurrency Ping-Ke Shih
2023-04-01 12:44 ` [PATCH 1/7] wifi: rtw88: add bitmap for dynamic port settings Ping-Ke Shih
2023-04-01 12:44 ` [PATCH 2/7] wifi: rtw88: add port switch for AP mode Ping-Ke Shih
2023-04-12 12:35 ` Kalle Valo
2023-04-01 12:44 ` [PATCH 3/7] wifi: rtw88: 8822c: extend reserved page number Ping-Ke Shih
2023-04-01 12:44 ` [PATCH 4/7] wifi: rtw88: disallow scan and PS during AP mode Ping-Ke Shih
2023-04-12 12:39 ` Kalle Valo [this message]
2023-04-14 12:21 ` Ping-Ke Shih
2023-04-01 12:44 ` [PATCH 5/7] wifi: rtw88: refine reserved page flow for " Ping-Ke Shih
2023-04-01 12:44 ` [PATCH 6/7] wifi: rtw88: prevent scan abort with other VIFs Ping-Ke Shih
2023-04-01 12:44 ` [PATCH 7/7] wifi: rtw88: 8822c: add iface combination Ping-Ke Shih
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=877cuh8eb3.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.com \
--cc=pkshih@realtek.com \
--cc=tony0620emma@gmail.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).