From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Alexander Wilhelm" <alexander.wilhelm@westermo.com>,
"Jeff Johnson" <jjohnson@kernel.org>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: Missing BEACON_LOSS event
Date: Wed, 30 Jul 2025 09:52:16 +0200 [thread overview]
Message-ID: <DBP862N3JBT3.2NRSJ8BECF0YI@gmail.com> (raw)
In-Reply-To: <aIjGvT+yQkZf8/Xs@FUE-ALEWI-WINX>
On Tue Jul 29, 2025 at 3:03 PM CEST, Alexander Wilhelm wrote:
> Hello devs,
>
> can someone help with the following issue?
>
> I'm using a QCN9074-based device in STA mode, connected to an access point. When
> the AP is powered off (without sending a deauthentication frame), the client
> remains indefinitely associated. There is no disconnect, no beacon loss event,
> and the RSSI remains stuck at the last known value.
[...]
> From what I can tell, the function `ath11k_mac_handle_beacon_miss()` exists and
> is wired up via `ath11k_roam_event()`, but the firmware never seems to send
> `WMI_ROAM_EVENTID`, so the handler is never triggered.
>
> Is this expected behavior? Does the firmware need to be configured differently
> to enable beacon miss detection in STA mode? Or is this a known limitation? Any
> help or clarification would be appreciated.
Hello,
I've brought this up already on the ath11k/ath12k list:
https://lore.kernel.org/ath12k/CZA2NS7J83D4.18SU6W9R96KPY@gmail.com/
To my knowlege, nothing upstream has been posted so far by QCA.
In non mainline sources there is a patch to support ath12k:
https://git.codelinaro.org/clo/qsdk/oss/system/feeds/wlan-open/-/blob/win.wlan_host_opensource.3.0/patches/ath12k/897-wifi-ath12k-Add-support-for-STA-mode-to-trigger.patch
My guess is that ath11k works the same way.
It would be great if QCA people could mainline this, it seems like a small
enough and isolated feature that could be pushed without side effects.
>
>
> Best regards
> Alexander Wilhelm
next prev parent reply other threads:[~2025-07-30 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 13:03 Missing BEACON_LOSS event Alexander Wilhelm
2025-07-30 7:52 ` Nicolas Escande [this message]
2025-07-30 9:00 ` Alexander Wilhelm
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=DBP862N3JBT3.2NRSJ8BECF0YI@gmail.com \
--to=nico.escande@gmail.com \
--cc=alexander.wilhelm@westermo.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-wireless@vger.kernel.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