From: Ping-Ke Shih <pkshih@realtek.com>
To: Martin Rodriguez Reboredo <yakoyoku@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtl8xxxu: toggle P2P for supported devices
Date: Thu, 26 Jun 2025 01:27:40 +0000 [thread overview]
Message-ID: <0083530d59084b82bebde68a73877568@realtek.com> (raw)
In-Reply-To: <20250625142541.44795-1-yakoyoku@gmail.com>
Martin Rodriguez Reboredo <yakoyoku@gmail.com> wrote:
> This is a MR to see if rtl8xxxu can be made to support P2P.
Sorry. What is MR?
>
> Theoretically this should be handled by mac80211 but it seems that
> drivers may have to take some extra steps depending on which device we
> are talking about. I know that this patch is so basic that it might be
> missing some H2C commands or similar for this to work on Realtek chips
> but I don't have the required knowledge for me to implement it, so if
> you know a place to read about I'll be glad to hear.
The commit message looks informal. Just describe why/what patch does.
If you want to share more information to readers, add information after
s-o-b with "---".
Basically if a WiFi device can support station and AP modes, it can
also support P2P mode. To work well, it needs to support additional
P2P PS, such as NoA, which needs some H2C commands or registers to
achieve. I'm not sure if chips supported by rtl8xxxu have these.
>
> As of now only rtl8192ex devices have their P2P_CLIENT and P2P_GO wiphy
> interface modes ensured because those are the only ones I can test on
> my rtl8192eu card. The rest of chips have them set from what I've seen
> in a cursory Internet search, they might or might not work.
Not sure what you really tested (I have seen another thread). Please mention
what you tested in commit message.
>
> Signed-off-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
---
(add things you want to share)
> ---
> drivers/net/wireless/realtek/rtl8xxxu/8188e.c | 1 +
> drivers/net/wireless/realtek/rtl8xxxu/8188f.c | 1 +
> drivers/net/wireless/realtek/rtl8xxxu/8192c.c | 1 +
> drivers/net/wireless/realtek/rtl8xxxu/8192e.c | 1 +
> drivers/net/wireless/realtek/rtl8xxxu/8192f.c | 1 +
> drivers/net/wireless/realtek/rtl8xxxu/8710b.c | 1 +
> drivers/net/wireless/realtek/rtl8xxxu/8723a.c | 1 +
> drivers/net/wireless/realtek/rtl8xxxu/8723b.c | 1 +
> drivers/net/wireless/realtek/rtl8xxxu/core.c | 29 ++++++++++++++++++-
> .../net/wireless/realtek/rtl8xxxu/rtl8xxxu.h | 1 +
> 10 files changed, 37 insertions(+), 1 deletion(-)
>
next prev parent reply other threads:[~2025-06-26 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 14:25 [PATCH] wifi: rtl8xxxu: toggle P2P for supported devices Martin Rodriguez Reboredo
2025-06-25 16:01 ` Bitterblue Smith
2025-06-25 19:43 ` Martin Rodriguez Reboredo
2025-06-26 0:50 ` Ping-Ke Shih
2025-06-26 1:27 ` Ping-Ke Shih [this message]
2025-06-26 20:02 ` Martin Rodriguez Reboredo
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=0083530d59084b82bebde68a73877568@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yakoyoku@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