From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Mehmet Fide <mehmet.fide@gmail.com>
Cc: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
mehmet.fide@screeningeagle.com
Subject: Re: [PATCH ath-current 2/2] wifi: ath9k_htc: start ANI when an AP interface begins to beacon
Date: Mon, 19 Oct 2026 22:42:46 +0200 [thread overview]
Message-ID: <87h5ihv2ux.fsf@toke.dk> (raw)
In-Reply-To: <20261005072209.4101009-3-mehmet.fide@gmail.com>
Mehmet Fide <mehmet.fide@gmail.com> writes:
> From: Mehmet Fide <mehmet.fide@screeningeagle.com>
>
> ath9k_htc_vif_reconfig() re-arms ANI after a channel change when an AP
> interface beacons. mac80211 configures the channel before it enables
> the beacon, so during a normal AP start that never triggers, and the
> start from add_interface that the previous patch removed was cancelled
> by the same channel configuration: with hostapd, ANI and the periodic
> calibration it drives did not run in AP mode until a later channel
> change.
>
> Start ANI when the beacon is enabled. The channel and its calibration
> data are in place by then, which is the state vif_reconfig() re-arms
> it in, and remove_interface() already stops it with the last AP
> interface.
>
> Fixes: a236254c35f0 ("ath9k_htc: Add ANI for AP mode")
> Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
prev parent reply other threads:[~2026-10-19 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 7:22 [PATCH ath-current 0/2] wifi: ath9k_htc: start ANI for an AP interface at the right time Mehmet Fide
2026-10-05 7:22 ` [PATCH ath-current 1/2] wifi: ath9k_htc: do not start ANI before the first channel is set Mehmet Fide
2026-10-19 20:42 ` Toke Høiland-Jørgensen
2026-10-05 7:22 ` [PATCH ath-current 2/2] wifi: ath9k_htc: start ANI when an AP interface begins to beacon Mehmet Fide
2026-10-19 20:42 ` Toke Høiland-Jørgensen [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=87h5ihv2ux.fsf@toke.dk \
--to=toke@toke.dk \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mehmet.fide@gmail.com \
--cc=mehmet.fide@screeningeagle.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®