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 1/2] wifi: ath12k: report size 0 for unsupported target memory types
Date: Tue, 10 Nov 2026 01:21:20 +0100 [thread overview]
Message-ID: <20261110002121.90167-2-gsustek@gmail.com> (raw)
In-Reply-To: <20261110002121.90167-1-gsustek@gmail.com>
For a target memory segment of an unsupported type,
ath12k_qmi_alloc_target_mem_chunk() warns, clears the DMA address in
chunk->paddr and keeps the requested size. The response then carries
address 0 with a non-zero size for that segment.
QCN9274 firmware WLAN.WBE.1.6-01243 requests such a segment at every
boot: type 0xa (QMI_WLFW_AFC_MEM_V01), 8 KiB for an Automated Frequency
Coordination response, which ath12k does not support:
ath12k_wifi7_pci 0000:06:00.0: memory type 10 not supported
The firmware treats a non-zero size as a provided region and maps the
given address. Nothing visible follows with this firmware: memory ready,
firmware ready and all radios come up with or without this change. The
response is still wrong, since it claims a region the host did not
provide.
Clear the size as well, so that an unsupported type is answered with
address 0 and size 0, which the firmware treats as not provided. The
warning is unchanged.
Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.6-01243-QCAHKSWPL_SILICONZ-1
Signed-off-by: Goran Sustek <gsustek@gmail.com>
---
v3: size cleared in the default case, no AFC case; warning kept;
message reworded (Rameshkumar Sundaram)
v2: no allocation, size 0 (Rameshkumar Sundaram)
drivers/net/wireless/ath/ath12k/qmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ath12k/qmi.c b/drivers/net/wireless/ath/ath12k/qmi.c
index 52a925fc44ee..4aaee5870ae9 100644
--- a/drivers/net/wireless/ath/ath12k/qmi.c
+++ b/drivers/net/wireless/ath/ath12k/qmi.c
@@ -2792,6 +2792,7 @@ static int ath12k_qmi_alloc_target_mem_chunk(struct ath12k_base *ab)
chunk->type);
chunk->paddr = 0;
chunk->v.addr = NULL;
+ chunk->size = 0;
break;
}
}
--
2.56.0
next prev parent 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 [PATCH ath-next v3 0/2] wifi: ath12k: accept what newer QCN9274 firmware requests at boot Goran Sustek
2026-11-10 0:21 ` Goran Sustek [this message]
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-2-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®