public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Remi Pommarel <repk@triplefau.lt>
To: ath12k@lists.infradead.org
Cc: Remi Pommarel <repk@triplefau.lt>
Subject: [BUG] ath12k: CSA with blocktx disrupts TX on other bands
Date: Wed, 4 Feb 2026 17:31:28 +0100	[thread overview]
Message-ID: <aYN0YOwzxujAFtUN@pilgrim> (raw)

Hi,

With the single phy changes introduced for MLO support, both 2.4 GHz
and 5 GHz interfaces on the same dual-band chip now share the same
hardware queues, even when operating on separate bands.

As a result, when a Channel Switch Announcement (CSA) with blocktx
is triggered on one interface (e.g., the 5 GHz vif),
ieee80211_vif_block_queues_csa() pauses the shared HW queues. This
unintentionally blocks TX traffic on the other interface (e.g., the
2.4 GHz vif), despite it being on a different band.

I haven't tested it, but the same issue is expected to affect a single
MLO AP setup, where a CSA could inadvertently pause transmission across
all links.

To address this class of problem, the IEEE80211_HW_HANDLES_QUIET_CSA
flag was introduced. When set, it delegates queue pausing to the
firmware, avoiding unnecessary disruptions in multi-vif or MLO
scenarios. This approach is already used in iwlwifi/mvm, as seen in
commit bbd6d0f8bc51 ("wifi: iwlwifi: mvm: advertise
IEEE80211_HW_HANDLES_QUIET_CSA").

Thus, does the current ath12k firmware properly handle TX quiescing
allowing IEEE80211_HW_HANDLES_QUIET_CSA to be set ? Or does it need
to be handle at the driver level (likewise what has been done in
iwlwifi/mvm in the commit above) ?

Thanks.

-- 
Remi


                 reply	other threads:[~2026-02-04 16:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aYN0YOwzxujAFtUN@pilgrim \
    --to=repk@triplefau.lt \
    --cc=ath12k@lists.infradead.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