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 v5 08/10] wifi: rtw89: handle IEEE80211_TX_CTL_REQ_TX_STATUS frames for USB
Date: Wed, 5 Nov 2025 01:06:26 +0000 [thread overview]
Message-ID: <b4d6d329b6fb46f1913e31f9e0bdb5a1@realtek.com> (raw)
In-Reply-To: <20251104135720.321110-9-pchelkin@ispras.ru>
Fedor Pchelkin <pchelkin@ispras.ru> wrote:
> Frames flagged with IEEE80211_TX_CTL_REQ_TX_STATUS mean the driver has to
> report to mac80211 stack whether AP sent ACK for the null frame/probe
> request or not. It's not implemented in USB part of the driver yet.
>
> PCIe HCI has its own way of getting TX status incorporated into RPP
> feature, and it's always enabled there. Other HCIs need a different
> scheme based on processing C2H messages.
>
> Thus define a .tx_rpt_enabled flag indicating which HCIs need to enable a
> TX report feature. Currently it is USB only.
>
> Toggle a bit in the TX descriptor and place flagged skbs in a fix-sized
> queue to wait for a message from the firmware. Firmware maintains a 4-bit
> sequence number for required frames hence the queue can contain just 16
> elements simultaneously. That's enough for normal driver / firmware
> communication. If the firmware crashes for any reason and doesn't provide
> TX reports in time, driver will handle this and report the obsolete frames
> as dropped.
>
> rtw89 also has a new feature providing a TX report for each transmission
> attempt. Ignore a failed TX status reported by the firmware until retry
> limit is reached or successful status appears. When there is no success
> and the retry limit is reached, report the frame up to the wireless stack
> as failed eventually.
>
> HCI reset should stop all pending TX activity so forcefully flush the
> queue there.
>
> Found by Linux Verification Center (linuxtesting.org).
>
> Signed-off-by: Fedor Pchelkin <pchelkin@ispras.ru>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2025-11-05 1:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 13:57 [PATCH rtw-next v5 00/10] wifi: rtw89: improvements for USB part Fedor Pchelkin
2025-11-04 13:57 ` [PATCH rtw-next v5 01/10] wifi: rtw89: usb: use common error path for skbs in rtw89_usb_rx_handler() Fedor Pchelkin
2025-11-06 6:43 ` Ping-Ke Shih
2025-11-04 13:57 ` [PATCH rtw-next v5 02/10] wifi: rtw89: usb: fix leak in rtw89_usb_write_port() Fedor Pchelkin
2025-11-04 13:57 ` [PATCH rtw-next v5 03/10] wifi: rtw89: usb: use ieee80211_free_txskb() where appropriate Fedor Pchelkin
2025-11-04 13:57 ` [PATCH rtw-next v5 04/10] wifi: rtw89: refine rtw89_core_tx_wait_complete() Fedor Pchelkin
2025-11-04 13:57 ` [PATCH rtw-next v5 05/10] wifi: rtw89: implement C2H TX report handler Fedor Pchelkin
2025-11-04 13:57 ` [PATCH rtw-next v5 06/10] wifi: rtw89: fill TX descriptor of FWCMD in shortcut Fedor Pchelkin
2025-11-04 13:57 ` [PATCH rtw-next v5 07/10] wifi: rtw89: usb: anchor TX URBs Fedor Pchelkin
2025-11-04 13:57 ` [PATCH rtw-next v5 08/10] wifi: rtw89: handle IEEE80211_TX_CTL_REQ_TX_STATUS frames for USB Fedor Pchelkin
2025-11-05 1:06 ` Ping-Ke Shih [this message]
2025-11-04 13:57 ` [PATCH rtw-next v5 09/10] wifi: rtw89: provide TX reports for management frames Fedor Pchelkin
2025-11-04 13:57 ` [PATCH rtw-next v5 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=b4d6d329b6fb46f1913e31f9e0bdb5a1@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®