From: Ping-Ke Shih <pkshih@realtek.com>
To: Fedor Pchelkin <pchelkin@ispras.ru>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>
Cc: Zong-Zhe Yang <kevin_yang@realtek.com>,
Bernie Huang <phhuang@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: RE: [PATCH rtw-next v4 05/10] wifi: rtw89: implement C2H TX report handler
Date: Mon, 3 Nov 2025 02:13:55 +0000 [thread overview]
Message-ID: <ae325e6c63604498b3bd2836f9662d23@realtek.com> (raw)
In-Reply-To: <20251029190241.1023856-6-pchelkin@ispras.ru>
Fedor Pchelkin <pchelkin@ispras.ru> wrote:
> rtw89 has several ways of handling TX status report events. The first one
> is based on RPP feature which is used by PCIe HCI. The other one depends
> on firmware sending a corresponding C2H message, quite similar to what
> rtw88 has.
>
> Toggle a bit in the TX descriptor to indicate to the firmware that TX
> report for the frame is expected. This will allow handling TX wait skbs
> and the ones flagged with IEEE80211_TX_CTL_REQ_TX_STATUS correctly.
>
> Do the bulk of the patch according to the vendor driver for RTL8851BU.
> However, there are slight differences in C2H message format between
> different types of chips. RTL885xB ones follow format V0. RTL8852C has
> format V1, and RTL8922AU has format V2.
>
> Found by Linux Verification Center (linuxtesting.org).
>
> Suggested-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Signed-off-by: Fedor Pchelkin <pchelkin@ispras.ru>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2025-11-03 2:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 19:02 [PATCH rtw-next v4 00/10] wifi: rtw89: improvements for USB part Fedor Pchelkin
2025-10-29 19:02 ` [PATCH rtw-next v4 01/10] wifi: rtw89: usb: use common error path for skbs in rtw89_usb_rx_handler() Fedor Pchelkin
2025-10-29 19:02 ` [PATCH rtw-next v4 02/10] wifi: rtw89: usb: fix leak in rtw89_usb_write_port() Fedor Pchelkin
2025-10-29 19:02 ` [PATCH rtw-next v4 03/10] wifi: rtw89: usb: use ieee80211_free_txskb() where appropriate Fedor Pchelkin
2025-10-29 19:02 ` [PATCH rtw-next v4 04/10] wifi: rtw89: refine rtw89_core_tx_wait_complete() Fedor Pchelkin
2025-10-29 19:02 ` [PATCH rtw-next v4 05/10] wifi: rtw89: implement C2H TX report handler Fedor Pchelkin
2025-11-03 2:13 ` Ping-Ke Shih [this message]
2025-10-29 19:02 ` [PATCH rtw-next v4 06/10] wifi: rtw89: fill TX descriptor of FWCMD in shortcut Fedor Pchelkin
2025-10-29 19:02 ` [PATCH rtw-next v4 07/10] wifi: rtw89: usb: anchor TX URBs Fedor Pchelkin
2025-11-03 2:26 ` Ping-Ke Shih
2025-10-29 19:02 ` [PATCH rtw-next v4 08/10] wifi: rtw89: handle IEEE80211_TX_CTL_REQ_TX_STATUS frames for USB Fedor Pchelkin
2025-11-03 3:05 ` Ping-Ke Shih
2025-10-29 19:02 ` [PATCH rtw-next v4 09/10] wifi: rtw89: provide TX reports for management frames Fedor Pchelkin
2025-10-29 19:02 ` [PATCH rtw-next v4 10/10] wifi: rtw89: process TX wait skbs for USB via C2H handler Fedor Pchelkin
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=ae325e6c63604498b3bd2836f9662d23@realtek.com \
--to=pkshih@realtek.com \
--cc=kevin_yang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=phhuang@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
all inboxes | Powered by JetHome®