From: Goran Sustek <gsustek@gmail.com>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH ath-next 0/3] wifi: ath12k: accept what newer QCN9274 firmware requests at boot
Date: Fri, 30 Oct 2026 23:08:21 +0100 [thread overview]
Message-ID: <20261030220824.915760-1-gsustek@gmail.com> (raw)
With QCN9274 firmware WLAN.WBE.1.6-01243 (the newest in
ath12k-firmware) the driver logs three warnings at every boot:
ath12k_wifi7_pci 0000:06:00.0: memory type 10 not supported
ath12k_wifi7_pci 0000:06:00.0: Invalid module id 2
ath12k_wifi7_pci 0000:06:00.0: failed to parse tlv -22
The firmware is not at fault: it requests the AFC memory region
(QMI memory type 10) and advertises a direct buffer ring for CV
upload (module 2), both defined in Qualcomm's interface headers but
not yet known to the driver.
Patch 1 allocates the AFC region instead of answering with a NULL
address. Patch 2 makes the DMA ring capability parser skip unknown
module IDs instead of aborting the event, and fixes the zero-filled
entry a plain skip would leave. Patch 3 names modules 2 and 3.
The idea of patch 2 was posted earlier by Nazar Mokrynskyi:
https://lore.kernel.org/linux-wireless/20260505172415.566328-3-nazar@mokrynskyi.com/
Tested on a QCN9274 hw2.0 PCI board (single device, AP MLD on 5 GHz
and 2.4 GHz) with the series on top of v7.3.1: all three warnings are
gone, the device comes up with both links, and there is no firmware
crash, call trace or IOMMU fault.
Goran Sustek (3):
wifi: ath12k: allocate the AFC memory region requested by firmware
wifi: ath12k: skip unknown direct buffer ring module IDs
wifi: ath12k: name direct buffer ring modules 2 and 3
drivers/net/wireless/ath/ath12k/qmi.c | 17 +++++++++++++
drivers/net/wireless/ath/ath12k/qmi.h | 3 ++
drivers/net/wireless/ath/ath12k/wmi.c | 43 +++++++++++++++++++++------------
drivers/net/wireless/ath/ath12k/wmi.h | 2 ++
4 files changed, 50 insertions(+), 15 deletions(-)
base-commit: 7b14c8f4a9615579b09cbcdc4515b65ae6124753
--
2.47.0
next reply other threads:[~2026-10-30 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 22:08 Goran Sustek [this message]
2026-10-30 22:08 ` [PATCH ath-next 1/3] wifi: ath12k: allocate the AFC memory region requested by firmware Goran Sustek
2026-10-30 22:08 ` [PATCH ath-next 2/3] wifi: ath12k: skip unknown direct buffer ring module IDs Goran Sustek
2026-10-30 22:08 ` [PATCH ath-next 3/3] wifi: ath12k: name direct buffer ring modules 2 and 3 Goran Sustek
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=20261030220824.915760-1-gsustek@gmail.com \
--to=gsustek@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®