From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Abdurrahman Karadag" <abdurrahmankaradag19@gmail.com>,
linux-wireless@vger.kernel.org
Cc: pkshih@realtek.com, linux-kernel@vger.kernel.org,
rtl8821cerfe2@gmail.com
Subject: Re: [PATCH rtw-next v4] wifi: rtw88: pci: wake the TX queues after restart_hw and interface up
Date: Wed, 21 Oct 2026 13:15:10 +0000 [thread overview]
Message-ID: <d62975cc45c5b17a85f1e5cb7f9c1e326f27ffa5@linux.dev> (raw)
In-Reply-To: <20261021101315.1974894-1-abdurrahmankaradag19@gmail.com>
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
next prev parent reply other threads:[~2026-10-21 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 10:13 [PATCH rtw-next v4] wifi: rtw88: pci: wake the TX queues after restart_hw and interface up Abdurrahman Karadag
2026-10-21 13:15 ` Luka Gejak [this message]
2026-10-21 15:03 ` Abdurrahman Karadag
2026-10-22 1:36 ` Ping-Ke Shih
2026-10-23 11:02 ` Abdurrahman Karadag
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=d62975cc45c5b17a85f1e5cb7f9c1e326f27ffa5@linux.dev \
--to=luka.gejak@linux.dev \
--cc=abdurrahmankaradag19@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.