Linux wireless drivers development
 help / color / mirror / Atom feed
From: Mehmet Fide <mehmet.fide@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mehmet Fide <mehmet.fide@screeningeagle.com>
Subject: Re: [PATCH rtw-next v3] wifi: rtw88: usb: route bmc frames via the high queue only for DTIM delivery
Date: Sun,  6 Sep 2026 10:20:17 +0200	[thread overview]
Message-ID: <20260906082017.909554-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <070f9724ca4a42a0b64bbf63724d8cdc@realtek.com>

Hi Ping-Ke,

> FYI. I checked vendor driver. Normally REG_ATIMWND sets 0xa or 0xc in AP mode
> for chips.

Thanks, that matches what I measured: 0x04 already drained the storm, so
0xa leaves comfortable headroom. If you agree I will add a small third patch
to the series that programs REG_ATIMWND to 0xa when the interface goes into
AP mode, as a complement to the bound and the filter (each covers a
different failure mode: the window adds drain capacity, the bound protects
the pool if the window is not enough, the filter keeps the ordinary chatter
off the beacon-paced path altogether).

> As you saw it is for TDLS channel switching (timeslot sharing), I
> don't think it can work in AP mode...
> I will ask USB experts internally to see if there is an interrupt
> to notify driver about TBTT (or beacon early).

Understood, and thank you for asking. If such a notification exists I would
be glad to prototype IEEE80211_HW_HOST_BROADCAST_PS_BUFFERING on top of it
as the long-term solution; the bound and filter series does not depend on it.

Mehmet

  reply	other threads:[~2026-09-06  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  5:34 [PATCH rtw-next v3] wifi: rtw88: usb: route bmc frames via the high queue only for DTIM delivery Mehmet Fide
2026-08-14  6:37 ` Mehmet Fide
2026-08-17  2:57   ` Ping-Ke Shih
2026-08-17  3:00 ` Ping-Ke Shih
2026-08-28 19:10 ` Mehmet Fide
2026-09-01  5:24   ` Ping-Ke Shih
2026-09-01  9:18     ` Mehmet Fide
2026-09-06  3:07       ` Ping-Ke Shih
2026-09-06  8:20         ` Mehmet Fide [this message]
2026-09-07  1:42           ` Ping-Ke Shih
2026-09-07  2:14             ` Ping-Ke Shih
2026-09-02  2:38 ` 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=20260906082017.909554-1-mehmet.fide@gmail.com \
    --to=mehmet.fide@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mehmet.fide@screeningeagle.com \
    --cc=pkshih@realtek.com \
    --cc=rtl8821cerfe2@gmail.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