public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Ping-Ke Shih <pkshih@realtek.com>
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 17:02:44 -0300	[thread overview]
Message-ID: <22784267.EfDdHjke4D@tx3000mach.io> (raw)
In-Reply-To: <0083530d59084b82bebde68a73877568@realtek.com>

[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]

On Wednesday 25 June 2025 22:27:40 Argentina Standard Time Ping-Ke Shih wrote:
> 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?

Merge request in GitLab's jargon, like PR.

>> 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 "---".

I admit that it doesn't look as a proper commit message, I'll take it into 
account in the next version of the patch.

> 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.

Many of these chips do have them, per some of the alternative drivers for them 
show in their sources. Perhaps in another patch some methods could be added to 
`rtl8xxxu_fileops`.

> [...]

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2025-06-26 20:03 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
2025-06-26 20:02   ` Martin Rodriguez Reboredo [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=22784267.EfDdHjke4D@tx3000mach.io \
    --to=yakoyoku@gmail.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@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