Re: Missing BEACON_LOSS event

["Nicolas Escande" <nico.escande@gmail.com>]

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