[PATCH rtw-next v4] wifi: rtw88: pci: wake the TX queues after restart_hw and interface up

[PATCH rtw-next v4] wifi: rtw88: pci: wake the TX queues after restart_hw and interface up

[Abdurrahman Karadag]

When a TX ring fills, rtw_pci_tx_write() stops the mac80211 queue and
records it in ring->queue_stopped. The completion loop in
rtw_pci_tx_isr() is what clears them, and it needs a descriptor to
complete. If the device goes down first, rtw_pci_dma_release() rewinds
the indices and frees what was in flight, so nothing is left that
could. ieee80211_reconfig() does not help either: it wakes only
IEEE80211_QUEUE_STOP_REASON_SUSPEND, and an interface down/up does not
reach it at all. TX then stays dead although the device came back.

Reset that state where the device starts, which both
ieee80211_restart_hw() and an interface down/up reach through
rtw_core_start(). Wake only when a ring was recorded as stopped:
mac80211 keeps a single non-refcounted DRIVER stop per queue, so an
unconditional wake here would also release the stop that
rtw_hw_scan_start() takes before it reaches rtw_pci_start() from idle.

Signed-off-by: Abdurrahman Karadag <abdurrahmankaradag19@gmail.com>
---
v4:
 - reset the flags and wake from rtw_pci_start() instead of
   rtw_reconfig_complete(), so an interface down/up is covered as well
   (Ping-Ke Shih)
 - name restart_hw in the subject (Ping-Ke Shih)

v3: wake from rtw_reconfig_complete() on RECONFIG_TYPE_RESTART
v2: wake from rtw_pci_reset_trx_ring(), gated on ring->queue_stopped
v1: https://lore.kernel.org/linux-wireless/20261002231013.11792-1-abdurrahmankaradag19@gmail.com/

 drivers/net/wireless/realtek/rtw88/pci.c | 8 ++++++++
 1 file changed, 8 insertions(+)

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);
 	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

Re: [PATCH rtw-next v4] wifi: rtw88: pci: wake the TX queues after restart_hw and interface up

[Luka Gejak]

October 21, 2026 at 12:13 PM, "Abdurrahman Karadag" <abdurrahmankaradag19@gmail.com> wrote:

> Wake only when a ring was recorded as stopped:
> mac80211 keeps a single non-refcounted DRIVER stop per queue, so an
> unconditional wake here would also release the stop that
> rtw_hw_scan_start() takes before it reaches rtw_pci_start() from idle.

The gated wake still releases that stop when a ring was left stopped. A
stalled ring followed by a disconnect keeps queue_stopped set through
rtw_enter_ips(), and the next scan from idle then does:

        rtw_hw_scan_start()
          ieee80211_stop_queues()
          rtw_core_scan_start()
            rtw_leave_ips()
              rtw_core_start()
                rtw_pci_start()
                  ieee80211_wake_queues()

Nothing transmits in idle, so this is harmless, but the v3 thread settled
on saying the wake can't be narrowed to the queue the ring-full path
stopped. Could the message say that, rather than suggest the gate keeps
the scan stop intact?

Other than that I have no objections with the code itself.

Best regards,
Luka Gejak