Received-SPF: pass (google.com: domain of linux-wireless+bounces-180-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
From: Ping-Ke Shih <pkshih@realtek.com>
To: Jay Sweat <jjsweat@outlook.com>
CC: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Realtek 8822ce p2p support
Thread-Topic: Realtek 8822ce p2p support
Thread-Index: AQHaHJ6/35nL8BzLVE+iP+/w63/TCrCFjBhAgAEOZs2AAHCucIAJI5tagABKzWA=
Date: Wed, 29 Nov 2023 00:33:48 +0000
Message-ID: <1f6b255e8c8a4d9c9d2af80c93b7acf0@realtek.com>
References: <IA1PR20MB5049CDB1D4CBA0FD5B68F15DA8BBA@IA1PR20MB5049.namprd20.prod.outlook.com>
 <16c31bac7aaf4c20917f500d6d2a52c2@realtek.com>
 <IA1PR20MB50490BFFD9F797722C9688BAA8BAA@IA1PR20MB5049.namprd20.prod.outlook.com>
 <5ffd01e6c8a1464795d612de1c6fa8a4@realtek.com>
 <IA1PR20MB50496D7A5578AC9DC1AE7370A8BCA@IA1PR20MB5049.namprd20.prod.outlook.com>
In-Reply-To: <IA1PR20MB50496D7A5578AC9DC1AE7370A8BCA@IA1PR20MB5049.namprd20.prod.outlook.com>
Accept-Language: en-US, zh-TW
Content-Language: zh-TW
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
MIME-Version: 1.0


> -----Original Message-----
> From: Jay Sweat <jjsweat@outlook.com>
> Sent: Wednesday, November 29, 2023 3:50 AM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: linux-wireless@vger.kernel.org
> Subject: Re: Realtek 8822ce p2p support
>=20
> That seems to have worked. P2P is now listed under supported interface mo=
des and gnome-network-displays
> works without issue. Havent noticed any other changes or any issues with =
P2P, but I only have the one app
> to test with.

Good to hear the news. More tests you can do are to make connection with
various devices, and try to play as GO and GC respectively. This can set
p2p_go_intent (0~15) in wpa_supplicant.conf to decide how a device
intents to be a GO. Then, use 'iw info' to check the role.

An advance test is to configure peer as concurrency that connects to an
AP, and the make another interface as P2P. A simple way is to take an
Android phone, and enter P2P connection setting page to make P2P connection
first, and then connect to an AP. The order of connection is important,
because different connected channels of P2P and AP make thing complicated,
and I suppose current code can't handle this case properly. Also, try
to be GO and GC in this scenario.=20

Ping-Ke