Re: [PATCH ath-next] wifi: ath9k_htc: do not fetch the beacon of a finished countdown
From: Toke Høiland-Jørgensen
Date: Tue Nov 17 2026 - 08:57:20 EST
Mehmet Fide <mehmet.fide@xxxxxxxxx> writes:
> Hi Toke,
>
>> if (ath9k_htc_csa_is_finished(priv))
>> return;
>
> That would skip one beacon at most. ath9k_htc_csa_is_finished() clears
> csa_vif when it calls ieee80211_csa_finish(), but csa_active stays set
> until the second round of __ieee80211_csa_finalize(), after the channel
> change, and ath9k_htc_set_channel() turns beaconing back on in between.
> The next SWBA finds csa_vif NULL and fetches the CSA beacon again.
Hmm, so it seems that the ath9k driver used to have a similar structure
(with the csa_vif pointer), but that was changed in commit:
4effc6fda7ab ("ath9k: prepare for multi-interface CSA support")
I think doing a similar change in ath9k_htc would allow us to have the
pre-check use the same function without this issue, *and* get rid of the
setting of csa_vif without any locks protecting it, no?
-Toke