From: Ping-Ke Shih <pkshih@realtek.com>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
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 v2 7/7] wifi: rtw89: process TX wait skbs for USB via C2H handler
Date: Mon, 13 Oct 2025 00:59:31 +0000 [thread overview]
Message-ID: <04b364eb49a4465a826fdc92e5ca5680@realtek.com> (raw)
In-Reply-To: <20251011175758-9e1b3340d51ac93a2663a800-pchelkin@ispras>
Fedor Pchelkin <pchelkin@ispras.ru> wrote:
> On Tue, 07. Oct 08:07, Ping-Ke Shih wrote:
> > Fedor Pchelkin <pchelkin@ispras.ru> wrote:
> > > @@ -1173,7 +1173,8 @@ int rtw89_core_tx_kick_off_and_wait(struct rtw89_dev *rtwdev, struct sk_buff *sk
> > >
> > > if (time_left == 0) {
> > > ret = -ETIMEDOUT;
> > > - list_add_tail(&wait->list, &rtwdev->tx_waits);
> > > + if (!rtwdev->hci.tx_rpt_enable)
> > > + list_add_tail(&wait->list, &rtwdev->tx_waits);
> >
> > Oh. You avoid using rtwdev->tx_waits for USB. But I'd like to have the same
> > behavior as PCIE.
>
> I may be confused but doesn't it conflict with the comment [1] you've
> posted to the previous version? I've treated that as we should use
> rtwdev->tx_rpt_queue for both TX wait and IEEE80211_TX_CTL_REQ_TX_STATUS
> frames...
Yes. I got this thought after reviewing whole v2.
>
> I'm all for following the PCIe-style as possible, too, but then initial
> comment [1] becomes irrelevant, right?
>
> [1]: https://lore.kernel.org/linux-wireless/c2c40bed311c4f05948cf2541c64ea30@realtek.com/
At the [1], I wanted to iterate skb's in rtwdev->tx_rpt_queue, and then call
rtw89_core_tx_wait_complete() if 'wait' existing in RTW89_TX_SKB_CB().
I think the idea is similar, but I might not have clear picture at v1 review.
If you feel they are conflict, just check and discuss with new comments.
next prev parent reply other threads:[~2025-10-13 1:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 20:08 [PATCH rtw-next v2 0/7] wifi: rtw89: improvements for USB part Fedor Pchelkin
2025-10-02 20:08 ` [PATCH rtw-next v2 1/7] wifi: rtw89: usb: use common error path for skbs in rtw89_usb_rx_handler() Fedor Pchelkin
2025-10-07 2:46 ` Ping-Ke Shih
2025-10-02 20:08 ` [PATCH rtw-next v2 2/7] wifi: rtw89: usb: fix leak in rtw89_usb_write_port() Fedor Pchelkin
2025-10-02 20:08 ` [PATCH rtw-next v2 3/7] wifi: rtw89: usb: use ieee80211_free_txskb() where appropriate Fedor Pchelkin
2025-10-07 2:51 ` Ping-Ke Shih
2025-10-02 20:08 ` [PATCH rtw-next v2 4/7] wifi: rtw89: refine rtw89_core_tx_wait_complete() Fedor Pchelkin
2025-10-07 2:54 ` Ping-Ke Shih
2025-10-02 20:08 ` [PATCH rtw-next v2 5/7] wifi: rtw89: implement C2H TX report handler Fedor Pchelkin
2025-10-07 3:13 ` Ping-Ke Shih
2025-10-02 20:08 ` [PATCH rtw-next v2 6/7] wifi: rtw89: handle IEEE80211_TX_CTL_REQ_TX_STATUS frames for USB Fedor Pchelkin
2025-10-07 6:31 ` Ping-Ke Shih
2025-10-14 21:23 ` Fedor Pchelkin
2025-10-15 1:43 ` Ping-Ke Shih
2025-10-15 7:51 ` Fedor Pchelkin
2025-10-16 0:54 ` Ping-Ke Shih
2025-10-17 10:06 ` Fedor Pchelkin
2025-10-02 20:08 ` [PATCH rtw-next v2 7/7] wifi: rtw89: process TX wait skbs for USB via C2H handler Fedor Pchelkin
2025-10-03 2:23 ` Zong-Zhe Yang
2025-10-07 8:07 ` Ping-Ke Shih
2025-10-11 16:06 ` Fedor Pchelkin
2025-10-13 0:59 ` Ping-Ke Shih [this message]
2025-10-04 17:37 ` [PATCH rtw-next v2 0/7] wifi: rtw89: improvements for USB part Bitterblue Smith
2025-10-11 14:57 ` Fedor Pchelkin
2025-10-11 22:49 ` Bitterblue Smith
2025-10-14 21:33 ` Fedor Pchelkin
2025-10-20 13:52 ` 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=04b364eb49a4465a826fdc92e5ca5680@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