From: marco.rodolfi@tuta.io
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Linux Wireless <linux-wireless@vger.kernel.org>,
Jay Sweat <jjsweat@outlook.com>
Subject: RE: Wireless P2P support for rtw88 families cards
Date: Fri, 9 Feb 2024 17:07:12 +0100 (CET) [thread overview]
Message-ID: <NqDbrXQ--3-9@tuta.io> (raw)
In-Reply-To: <161bc4c6ffe14a36ad76f214fe533eef@realtek.com>
Just recently managed to run a couple of tests on lwfinger fork of the driver, which still required a small modification to expose P2P to the host like:
diff --git a/main.c b/main.cindex f589029..e8d7079 100644--- a/main.c+++ b/main.c@@ -110,7 +110,9 @@ static const struct ieee80211_iface_limit rtw_iface_limits[] = { }, { .max = 1,- .types = BIT(NL80211_IFTYPE_AP),+ .types = BIT(NL80211_IFTYPE_AP) |+ BIT(NL80211_IFTYPE_P2P_CLIENT) |+ BIT(NL80211_IFTYPE_P2P_GO), } }; @@ -2366,6 +2368,9 @@ int rtw_register_hw(struct rtw_dev *rtwdev, struct ieee80211_hw *hw) if (rtwdev->chip->id == RTW_CHIP_TYPE_8822C) { hw->wiphy->iface_combinations = rtw_iface_combs; hw->wiphy->n_iface_combinations = ARRAY_SIZE(rtw_iface_combs);+ hw->wiphy->interface_modes = hw->wiphy->interface_modes |+ BIT(NL80211_IFTYPE_P2P_CLIENT) |+ BIT(NL80211_IFTYPE_P2P_GO); } wiphy_ext_feature_set(hw->wiphy, NL80211_EXT_FEATURE_CAN_REPLACE_PTK0);
I've limited this only on my specific chipset instead of all the supported chips, since just below there was a filter on the 8822c chip.
Initial tests seems good to me, P2P is exposed to userspace and a short test using wpa_supplicant show activity + my android phone seems to see the wireless direct network just fine and the connect prompts come in the wpa_supplicant logs, but pairing seems to always failing even inserting the code shown in the console. Not sure if I have to whitelist stuff from wpa_cli, can't really find much as user guide on the web regarding Wireless Direct.
I've tried mirrorcast as another usecase, but I can't seem to get it working correctly, the wpa_supplicant logs just claim that it can't be enabled on a non active interface during initialization (might just be an issue with mirrorcast itself rather than anything else tho).
I've posted this to a Deck user forums where other people had expressed their desire to test this, so I might get additional feedback to say if this is all that's needed to the driver or if it requires other stuff to be added.
No dmesg errors are printed anywhere, so this looks already quite good to me for now.
I'll probably follow this up soon as more data comes in,
Marco.
Dec 11, 2023, 02:30 by pkshih@realtek.com:
>
>
>> -----Original Message-----
>> From: marco.rodolfi@tuta.io <marco.rodolfi@tuta.io>
>> Sent: Sunday, December 10, 2023 2:55 AM
>> To: Larry Finger <Larry.Finger@lwfinger.net>
>> Cc: Linux Wireless <linux-wireless@vger.kernel.org>; Ping-Ke Shih <pkshih@realtek.com>
>> Subject: Re: Wireless P2P support for rtw88 families cards
>>
>> Oh, so there is already a test in. It's not in the main driver since it's missing testing or it's not that
>> much stable?
>>
>
> I don't have time to develop and test P2P on rtw88 that contains many chips.
>
> As thread [1], I did suggest some test cases, and I think Jay is testing.
>
> [1] https://lore.kernel.org/linux-wireless/1f6b255e8c8a4d9c9d2af80c93b7acf0@realtek.com/
>
prev parent reply other threads:[~2024-02-09 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 14:52 Wireless P2P support for rtw88 families cards marco.rodolfi
2023-12-09 18:34 ` Larry Finger
2023-12-09 18:55 ` marco.rodolfi
2023-12-11 1:29 ` Ping-Ke Shih
2024-02-09 16:07 ` marco.rodolfi [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=NqDbrXQ--3-9@tuta.io \
--to=marco.rodolfi@tuta.io \
--cc=Larry.Finger@lwfinger.net \
--cc=jjsweat@outlook.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 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).