Linux wireless drivers development
 help / color / mirror / Atom feed
From: Josef Schlehofer <pepe.schlehofer@gmail.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH rtw-next] wifi: rtw88: extend the TX report timeout to RTL8822BU
Date: Sun, 27 Sep 2026 06:38:08 +0200	[thread overview]
Message-ID: <91FCAEB4-16A4-411A-A436-0803F89F3B7D@gmail.com> (raw)
In-Reply-To: <3d24a4e461dd4e5fbb7aaac66aad1b0b@realtek.com>



> On 24. 9. 2026, at 02:49, Ping-Ke Shih <pkshih@realtek.com> wrote:
> 
> Hi Josef,
> 
> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
>> On 22/09/2026 05:03, Ping-Ke Shih wrote:
>>> Josef Schlehofer <pepe.schlehofer@gmail.com> wrote:
>>>> diff --git a/drivers/net/wireless/realtek/rtw88/tx.c b/drivers/net/wireless/realtek/rtw88/tx.c
>>>> index 4e110a457..55d7923e1 100644
>>>> --- a/drivers/net/wireless/realtek/rtw88/tx.c
>>>> +++ b/drivers/net/wireless/realtek/rtw88/tx.c
>>>> @@ -208,7 +208,8 @@ void rtw_tx_report_enqueue(struct rtw_dev *rtwdev, struct sk_buff *skb, u8 sn)
>>>>        __skb_queue_tail(&tx_report->queue, skb);
>>>>        spin_unlock_irqrestore(&tx_report->q_lock, flags);
>>>> 
>>>> -       if ((rtwdev->chip->id == RTW_CHIP_TYPE_8723D &&
>>>> +       if (((rtwdev->chip->id == RTW_CHIP_TYPE_8723D ||
>>>> +             rtwdev->chip->id == RTW_CHIP_TYPE_8822B) &&
>>>>             rtwdev->hci.type == RTW_HCI_TYPE_USB) ||
>>> 
>>> Hi Bitterblue,
>>> 
>>> It seems like more and more USB chips need this, let's enlarge timeout time
>>> for all USB devices. Do you have any concern? Need your input.
>>> 
>> 
>> It seems fine to me.
>> 
>>>>            rtw_is_8723bs(rtwdev))
>>> 
>>> Also, considering SDIO chips, should we keep original timeout for PCI only?
>>> 
>> 
>> This too.
>> 
> 
> I sent a patch [1]. Please test if it works to you. 
> If so, I'd take my one, and drop this.
> 
> [1] https://lore.kernel.org/linux-wireless/20260924004637.9958-1-pkshih@realtek.com/T/#u

It works for me. I tested it on the same TP-Link Archer T4U v3
(RTL8812BU, rtw_8822bu) , so please drop mine and take yours. 

If you would like, you can add:
Tested-by: Josef Schlehofer <pepe.schlehofer@gmail.com>

It would be nice to have it in the stable kernels, too.
Thanks!

Josef

      reply	other threads:[~2026-09-27  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 16:53 [PATCH rtw-next] wifi: rtw88: extend the TX report timeout to RTL8822BU Josef Schlehofer
2026-09-22  2:03 ` Ping-Ke Shih
2026-09-23 15:03   ` Bitterblue Smith
2026-09-24  0:49     ` Ping-Ke Shih
2026-09-27  4:38       ` Josef Schlehofer [this message]

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=91FCAEB4-16A4-411A-A436-0803F89F3B7D@gmail.com \
    --to=pepe.schlehofer@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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