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,
Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>,
Nazar Mokrynskyi <nazar@mokrynskyi.com>
Subject: [PATCH ath-next v3 0/2] wifi: ath12k: accept what newer QCN9274 firmware requests at boot
Date: Tue, 10 Nov 2026 01:21:19 +0100 [thread overview]
Message-ID: <20261110002121.90167-1-gsustek@gmail.com> (raw)
QCN9274 firmware WLAN.WBE.1.6-01243 requests two things at boot that
ath12k does not implement: a target memory segment of type 0xa (AFC)
and direct buffer rings for module IDs 2 and 3. Neither is needed for
operation. Today the first gets a wrong answer and the second aborts
the parse of the service ready ext event.
Patch 1 answers every unsupported memory type with size 0. Patch 2
skips unknown ring module IDs instead of failing the parse. Both keep
a warning, so the gap between firmware and driver stays visible.
v3:
- 1/2: clear the size in the default case, no AFC case; keep the
warning; describe only the response change (Rameshkumar Sundaram).
- 2/2: warn for a skipped entry instead of a debug message.
- Rebased on ath-next.
v2:
- 1/2: do not allocate the region, answer with size 0 (Rameshkumar
Sundaram); former 3/3 dropped.
- 2/2: commit message and comment reworded.
v2: https://lore.kernel.org/r/20261102200235.48973-1-gsustek@gmail.com
v1: https://lore.kernel.org/r/20261030220836.14164-1-gsustek@gmail.com
Goran Sustek (2):
wifi: ath12k: report size 0 for unsupported target memory types
wifi: ath12k: skip unknown direct buffer ring module IDs
drivers/net/wireless/ath/ath12k/qmi.c | 1 +
drivers/net/wireless/ath/ath12k/wmi.c | 43 +++++++++++++++++----------
2 files changed, 29 insertions(+), 15 deletions(-)
base-commit: d0fbb39d65dc9dcb4175fa6b23e473dec3670f4d
--
2.56.0
next reply other threads:[~2026-11-10 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 0:21 Goran Sustek [this message]
2026-11-10 0:21 ` [PATCH ath-next v3 1/2] wifi: ath12k: report size 0 for unsupported target memory types Goran Sustek
2026-11-10 0:21 ` [PATCH ath-next v3 2/2] wifi: ath12k: skip unknown direct buffer ring module IDs 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=20261110002121.90167-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 \
--cc=nazar@mokrynskyi.com \
--cc=rameshkumar.sundaram@oss.qualcomm.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®