mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mehmet Fide <mehmet.fide@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	mehmet.fide@screeningeagle.com
Subject: [PATCH ath-current 0/2] wifi: ath9k_htc: start ANI for an AP interface at the right time
Date: Mon,  5 Oct 2026 09:22:07 +0200	[thread overview]
Message-ID: <20261005072209.4101009-1-mehmet.fide@gmail.com> (raw)

From: Mehmet Fide <mehmet.fide@screeningeagle.com>

ath9k_htc starts ANI for an AP interface in add_interface, before a
channel and the calibration data exist. When the bring-up stalls
between add_interface and the first channel configuration, the first
ANI tick dereferences a NULL ah->caldata and the device does not
recover. Patch 1 removes that start. Patch 2 starts ANI once the
interface beacons, which is where ath9k_htc_vif_reconfig() already
re-arms it after a channel change; without it ANI and the periodic
calibration never ran during a normal AP start.

Tested with AR9271 on 6.18.48 and on a 6.12 product kernel: the oops
reproduces on every start with a 500 ms delay after add_interface and
is gone with the series; an hour as an AP, station mode, a channel
switch, hostapd disable/enable and a restart are clean.

Mehmet Fide (2):
  wifi: ath9k_htc: do not start ANI before the first channel is set
  wifi: ath9k_htc: start ANI when an AP interface begins to beacon

 drivers/net/wireless/ath/ath9k/htc_drv_main.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-10-05  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  7:22 Mehmet Fide [this message]
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-05  7:22 ` [PATCH ath-current 2/2] wifi: ath9k_htc: start ANI when an AP interface begins to beacon Mehmet Fide

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=20261005072209.4101009-1-mehmet.fide@gmail.com \
    --to=mehmet.fide@gmail.com \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mehmet.fide@screeningeagle.com \
    --cc=toke@toke.dk \
    /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®