mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Abdurrahman Karadag <abdurrahmankaradag19@gmail.com>
To: pkshih@realtek.com
Cc: linux-wireless@vger.kernel.org, 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: Fri, 23 Oct 2026 14:02:22 +0300	[thread overview]
Message-ID: <20261023110222.2804687-1-abdurrahmankaradag19@gmail.com> (raw)
In-Reply-To: <e9cab7ed7daf45b9b4c2294174f8c1a0@realtek.com>

> 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().

Done in v5 as rtw_pci_reset_tx_queue_state(), called first inside the
irq_lock section. It carries lockdep_assert_held(&rtwpci->irq_lock)
like rtw_pci_deep_ps_enter() does, to record that the caller holds it.

> Add an empty line before 'running = true'.

Done.

> For scanning from idle case, we have an assistant
> 'test_bit(RTW_FLAG_SCANNING, rtwdev->flags)' if you want.

The case is real - rtw_hw_scan_start() takes the stop before it reaches
rtw_core_scan_start(), so the stop is already standing when the start
runs. The flag is not: rtw_core_scan_start() calls rtw_leave_ips() and
only sets RTW_FLAG_SCANNING at the end of the same function, and that is
the one set_bit() for it in the driver. So the test would read false
exactly when the scan's stop is up, and I left it out rather than add a
check that cannot fire there.

      reply	other threads:[~2026-10-23 11:02 UTC|newest]

Thread overview: 5+ 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
2026-10-23 11:02   ` Abdurrahman Karadag [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=20261023110222.2804687-1-abdurrahmankaradag19@gmail.com \
    --to=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 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®