All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: Sascha Hauer <sha@pengutronix.de>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH 2/2] wifi: rtw88: Avoid using macid 0 in AP mode
Date: Tue, 20 Aug 2024 00:34:46 +0000	[thread overview]
Message-ID: <3e2d32e473204471af1814aa2ce26bcb@realtek.com> (raw)
In-Reply-To: <1377b2e9-4da2-45cb-86f5-5b80fe5ab025@maciej.szmigiero.name>

Hi Bitterblue,

Maciej S. Szmigiero <mail@maciej.szmigiero.name> wrote:
> I tested these patches on USB RTL8821CU and can confirm that the AP mode seems to
> work as good with your patch [2] as it did with the Bitterblue's one.
> 
> The only issue with either your or Bitterblue's patches is that I occasionally get the
> following messages in the kernel log in the AP mode:
> > kernel: [T1234] rtw_8821cu 4-1.2:1.2: error beacon valid
> > kernel: [T1234] rtw_8821cu 4-1.2:1.2: failed to download drv rsvd page
> > kernel: [T1234] rtw_8821cu 4-1.2:1.2: failed to download beacon
> 
> Around the time these messages are logged ping RTT of a connected (battery powered)
> STA climbs into multiple seconds range so I guess there might be something wrong
> with beacon DTIM update here.

Can you also see this in your side? It seems like download beacon for change of DTIM
might be failed occasionally. 

Ping-Ke


  reply	other threads:[~2024-08-20  0:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 22:49 [PATCH 1/2] wifi: rtw88: Fix USB devices not transmitting beacons Bitterblue Smith
2024-07-28 22:51 ` [PATCH 2/2] wifi: rtw88: Avoid using macid 0 in AP mode Bitterblue Smith
2024-07-30  6:33   ` Ping-Ke Shih
2024-07-30 12:55     ` Bitterblue Smith
2024-07-31  0:47       ` Ping-Ke Shih
2024-07-31 12:20         ` Bitterblue Smith
2024-08-08  9:38           ` Maciej S. Szmigiero
2024-08-19  2:59             ` Ping-Ke Shih
2024-08-19 21:20               ` Maciej S. Szmigiero
2024-08-20  0:34                 ` Ping-Ke Shih [this message]
2024-08-20 23:15                   ` Bitterblue Smith
2024-07-31  8:10       ` Ping-Ke Shih
2024-07-30  7:36 ` [PATCH 1/2] wifi: rtw88: Fix USB devices not transmitting beacons Ping-Ke Shih
2024-08-21  6:25 ` Ping-Ke Shih
2024-08-21  7:17   ` Michele Bisogno
2024-08-21 11:17   ` Bitterblue Smith

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=3e2d32e473204471af1814aa2ce26bcb@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mail@maciej.szmigiero.name \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=sha@pengutronix.de \
    /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.