All of lore.kernel.org
 help / color / mirror / Atom feed
From: andres parra <andres.parrab@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: andres parra <andres.parrab@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 0/4] wifi: rtw89: add NL80211_IFTYPE_P2P_DEVICE support
Date: Mon, 31 Aug 2026 19:50:43 +0200	[thread overview]
Message-ID: <20260831175044.208200-1-andres.parrab@gmail.com> (raw)
In-Reply-To: <fe4778c07f644ed38a03c467ef1293d7@realtek.com>

Hi Ping-Ke,

Thanks for the quick, detailed reply -- really appreciate it. I applied
patches 11-14 from your series (git am -p6 straight onto a clean sync
of core.c/core.h/chan.c/chan.h/debug.c/fw.c/ps.c/regd.c/util.h against
current mainline, since I don't have a full rtw-next checkout set up
yet) and tested on the same RTL8922AE hardware.

Results:

- Built clean, loaded clean, zero WARN/BUG in dmesg through the whole
  test.
- Real P2P-Device wdev appears (confirmed via `iw dev`), same as with
  my own patch.
- Real P2P discovery, GO negotiation (P2P-GO-NEG-SUCCESS), and full
  group formation against my actual Wi-Fi Display TV, tested twice:
  once with raw wpa_cli, once through a real WFD casting application
  (different encoder/bitrate settings each time). Both completed
  successfully, real DHCP lease on the resulting P2P-Client interface,
  real video actually displaying on the TV.
- No regression to normal STA association/roaming with your patches
  loaded.

On the two things I asked about:

1. Cross-band cost: confirmed reproducible with your patches too, and
   it matches your explanation exactly -- forced the STA link onto
   5GHz while the P2P-Client link stayed on 2.4GHz (same channel it
   started on), and casting became noticeably choppier, then smooth
   again once STA moved back to 2.4GHz. Consistent with TDMA timeslot
   sharing rather than a bug in either patch set.

2. Same-band channel-switch disconnect: reproduced it with your
   patches too, while writing this email. My AP did a real, ordinary
   channel switch on the STA link (CTRL-EVENT-STARTED-CHANNEL-SWITCH
   -> CTRL-EVENT-CHANNEL-SWITCH, 2462 MHz -> 2412 MHz, i.e. channel 11
   to channel 1, both 2.4 GHz), while the P2P-Client link was still
   active on channel 11. Result, same signature as with my own patch:

     p2p-wlanX-Y: CTRL-EVENT-BEACON-LOSS
     p2p-wlanX-Y: CTRL-EVENT-DISCONNECTED bssid=<GO> reason=4 locally_generated=1
     P2P-GROUP-REMOVED p2p-wlanX-Y client reason=IDLE

   No automatic recovery -- the group is gone, casting stops, no crash
   or kernel WARN/BUG (dmesg clean, system otherwise fully stable,
   STA link itself reconnects fine on the new channel). So this one is
   confirmed **not** fixed by patches 11-14 -- same behavior as
   before your series was applied. Happy to test whatever you'd
   suggest, or dig into rtw89_entity_mgnt/chan.c myself if that's
   useful, now that patch 11 gave me a clearer read on that code.

Test flow, as asked, for reference:
  wpa_cli -i p2p-dev-wlan0 p2p_find
  wpa_cli -i p2p-dev-wlan0 p2p_connect <TV MAC> pbc go_intent=0
  (watch for P2P-GO-NEG-SUCCESS / P2P-GROUP-STARTED in
  journalctl -u wpa_supplicant)
  -- then wait for or induce a real AP-side channel switch on the STA
  link (I couldn't force mine reliably; this one happened on its own
  from the AP), watch for CTRL-EVENT-CHANNEL-SWITCH on the STA link
  followed by whatever happens to the P2P-Client link.

Given your team already has a complete, working implementation with
real fixes I wouldn't have found on my own (the 6 GHz regd recalc
issue, the entity-pause/tracking interaction), I'll hold off on
pushing my own patches further -- happy to keep helping test yours on
real hardware instead, since that seems like the more useful thing I
can offer here. Thanks again for taking the time to look at this and
point me in the right direction.

Andres

  reply	other threads:[~2026-08-31 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 17:42 [RFC PATCH 0/4] wifi: rtw89: add NL80211_IFTYPE_P2P_DEVICE support andres parra
2026-08-22 17:42 ` [RFC PATCH 1/4] wifi: rtw89: declare P2P_DEVICE in interface modes/combinations andres parra
2026-08-22 17:42 ` [RFC PATCH 2/4] wifi: rtw89: map P2P_DEVICE to RTW89_WIFI_ROLE_P2P_DEVICE andres parra
2026-08-22 17:42 ` [RFC PATCH 3/4] wifi: rtw89: handle P2P_DEVICE in net_type/self_role switch andres parra
2026-08-22 17:42 ` [RFC PATCH 4/4] wifi: rtw89: raise RTW89_MAX_INTERFACE_NUM to 3 for P2P-Device concurrency andres parra
2026-08-26  7:03 ` [RFC PATCH 0/4] wifi: rtw89: add NL80211_IFTYPE_P2P_DEVICE support Ping-Ke Shih
2026-08-31 17:50   ` andres parra [this message]
2026-09-06  2:42     ` 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=20260831175044.208200-1-andres.parrab@gmail.com \
    --to=andres.parrab@gmail.com \
    --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 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.