From: Ping-Ke Shih <pkshih@realtek.com>
To: Mehmet Fide <mehmet.fide@gmail.com>
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@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: Mon, 7 Sep 2026 02:14:54 +0000 [thread overview]
Message-ID: <f7bb980260ed4225a31b8c2c980ccc49@realtek.com> (raw)
In-Reply-To: <d91b4f77a662442fa796f0407fe08d54@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> > > 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.
>
> I'm still checking this, and will give back to you if it exists.
I checked. The H2C and C2H can also be used to AP mode, not only TDLS channel
switching. You can spin this as long-term solution.
Ping-Ke
next prev parent reply other threads:[~2026-09-07 2:15 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
2026-09-07 1:42 ` Ping-Ke Shih
2026-09-07 2:14 ` Ping-Ke Shih [this message]
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=f7bb980260ed4225a31b8c2c980ccc49@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mehmet.fide@gmail.com \
--cc=mehmet.fide@screeningeagle.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 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.