From: Ping-Ke Shih <pkshih@realtek.com>
To: Doug Brewer <brewer.doug@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: rtw89: RTL8852BE P2P-device iftype and STA+P2P interface combination
Date: Mon, 29 Jun 2026 02:10:38 +0000 [thread overview]
Message-ID: <54e7877f76944bd29e57d6eafe5e3811@realtek.com> (raw)
In-Reply-To: <CAG0V13TRHzXtoMY=XZMOd=WjzS58Cu=aePFCz8mY6UoGYm5dXw@mail.gmail.com>
Doug Brewer <brewer.doug@gmail.com> wrote:
> Hi,
>
> I'm experimenting with Wi-Fi Display (Miracast sink) concurrent with an
> STA connection on an RTL8852BE (PCIe) using the mainline rtw89 driver
> (kernel 6.18.37).
>
> iw phy reports:
> Supported interface modes:
> * managed, AP, P2P-client, P2P-GO
> (no P2P-device)
> interface combinations are not supported
>
> In practice this blocks the standard P2P flow: there is no P2P-device
> iftype for a dedicated discovery context, and no advertised interface
> combination for managed + P2P-client coexistence.
>
> My questions:
> 1. is P2P-device iftype support planned for rtw89 on RTL885x? Is there a
> known technical blocker, or is it simply not yet implemented?
We are planning to add P2P-device iftype. It needs to consider the cases of
channel context, conditions of power save, and etc. It will take some time.
I think it would be okay that you use STA interface to do P2P negotiation,
and then create P2P-client or P2P-GO iftype then.
> 2. would advertising a managed + P2P-client interface combination
> (single channel) be feasible on the current rtw89?
This is a SCC which is supported.
> 3. is MCC (#channels > 1) on the roadmap, or considered out of scope?
Current support MCC as well. However, we are cooking new firmware to support
hw_scan with two operation channels -- which doesn't matter if you don't need
to do scan when MCC is operating.
Ping-Ke
next prev parent reply other threads:[~2026-06-29 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 6:37 rtw89: RTL8852BE P2P-device iftype and STA+P2P interface combination Doug Brewer
2026-06-29 2:10 ` Ping-Ke Shih [this message]
2026-06-29 4:49 ` Doug Brewer
2026-06-30 0:50 ` Ping-Ke Shih
2026-07-01 6:40 ` Doug Brewer
2026-07-01 14:06 ` Doug Brewer
2026-07-03 0:43 ` Ping-Ke Shih
2026-07-04 7:01 ` Doug Brewer
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=54e7877f76944bd29e57d6eafe5e3811@realtek.com \
--to=pkshih@realtek.com \
--cc=brewer.doug@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.