From: Ping-Ke Shih <pkshih@realtek.com>
To: Abdurrahman Karadag <abdurrahmankaradag19@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH rtw-next v4] wifi: rtw88: pci: wake the TX queues after restart_hw and interface up
Date: Thu, 22 Oct 2026 01:36:27 +0000 [thread overview]
Message-ID: <e9cab7ed7daf45b9b4c2294174f8c1a0@realtek.com> (raw)
In-Reply-To: <20261021101315.1974894-1-abdurrahmankaradag19@gmail.com>
Abdurrahman Karadag <abdurrahmankaradag19@gmail.com> wrote:
> diff --git a/drivers/net/wireless/realtek/rtw88/pci.c b/drivers/net/wireless/realtek/rtw88/pci.c
> index 66d2e5f..fd84ace 100644
> --- a/drivers/net/wireless/realtek/rtw88/pci.c
> +++ b/drivers/net/wireless/realtek/rtw88/pci.c
> @@ -571,12 +571,20 @@ static void rtw_pci_napi_stop(struct rtw_dev *rtwdev)
> static int rtw_pci_start(struct rtw_dev *rtwdev)
> {
> struct rtw_pci *rtwpci = (struct rtw_pci *)rtwdev->priv;
> + enum rtw_tx_queue_type queue;
> + bool wake = false;
>
> rtw_pci_napi_start(rtwdev);
>
> spin_lock_bh(&rtwpci->irq_lock);
It would look natural to clear queue_stopped before enabling interrupt,
since it is intended to reset. More, add a function to be clear that we
are resetting queue_stopped, like rtw_pci_reset_tx_{ring or queue}_state().
For scanning from idle case, we have an assistant
'test_bit(RTW_FLAG_SCANNING, rtwdev->flags)' if you want.
Add an empty line before 'running = true'.
> rtwpci->running = true;
> rtw_pci_enable_interrupt(rtwdev, rtwpci, false);
> + for (queue = 0; queue < RTK_MAX_TX_QUEUE_NUM; queue++) {
> + wake |= rtwpci->tx_rings[queue].queue_stopped;
> + rtwpci->tx_rings[queue].queue_stopped = false;
> + }
> + if (wake)
> + ieee80211_wake_queues(rtwdev->hw);
> spin_unlock_bh(&rtwpci->irq_lock);
>
> return 0;
> base-commit: 9b0be45d4d52fd223994e151f169743a97abd290
> --
> 2.56.0
prev parent reply other threads:[~2026-10-22 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 10:13 Abdurrahman Karadag
2026-10-21 13:15 ` Luka Gejak
2026-10-21 15:03 ` Abdurrahman Karadag
2026-10-22 1:36 ` Ping-Ke Shih [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=e9cab7ed7daf45b9b4c2294174f8c1a0@realtek.com \
--to=pkshih@realtek.com \
--cc=abdurrahmankaradag19@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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®