From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>
Subject: [PATCH ath-next 2/3] wifi: ath12k: clear chunk paddr and size in ath12k_qmi_free_target_mem_chunk()
Date: Thu, 30 Jul 2026 14:17:41 +0800 [thread overview]
Message-ID: <20260730-ath12k-align-qmi-memory-v1-2-0fef98dda614@oss.qualcomm.com> (raw)
In-Reply-To: <20260730-ath12k-align-qmi-memory-v1-0-0fef98dda614@oss.qualcomm.com>
paddr and size of a chunk are not cleared after the chunk is freed, which
is safe now since the code checks vaddr only and it is properly cleared
on free. However, leaving stale values can mislead diagnostics and future
maintenance. Clear both to reduce such risk, this also aligns with
ath12k_qmi_free_mlo_mem_chunk().
Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3
Tested-on: QCC2072 hw1.0 PCI WLAN.COL.1.0.c2-00074-QCACOLSWPL_V1_TO_SILICONZ-1
Signed-off-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
---
drivers/net/wireless/ath/ath12k/qmi.c | 26 ++++++++++++++++----------
1 file changed, 16 insertions(+), 10 deletions(-)
diff --git a/drivers/net/wireless/ath/ath12k/qmi.c b/drivers/net/wireless/ath/ath12k/qmi.c
index f96d847ac92f..03ec2057ca27 100644
--- a/drivers/net/wireless/ath/ath12k/qmi.c
+++ b/drivers/net/wireless/ath/ath12k/qmi.c
@@ -2602,27 +2602,33 @@ static void ath12k_qmi_free_mlo_mem_chunk(struct ath12k_base *ab,
static void ath12k_qmi_free_target_mem_chunk(struct ath12k_base *ab)
{
struct ath12k_hw_group *ag = ab->ag;
+ struct target_mem_chunk *chunk;
int i, mlo_idx;
for (i = 0, mlo_idx = 0; i < ab->qmi.mem_seg_count; i++) {
- if (ab->qmi.target_mem[i].type == MLO_GLOBAL_MEM_REGION_TYPE) {
+ chunk = &ab->qmi.target_mem[i];
+
+ if (chunk->type == MLO_GLOBAL_MEM_REGION_TYPE) {
ath12k_qmi_free_mlo_mem_chunk(ab,
- &ab->qmi.target_mem[i],
+ chunk,
mlo_idx++);
} else {
if (test_bit(ATH12K_FLAG_FIXED_MEM_REGION, &ab->dev_flags) &&
- ab->qmi.target_mem[i].v.ioaddr) {
- iounmap(ab->qmi.target_mem[i].v.ioaddr);
- ab->qmi.target_mem[i].v.ioaddr = NULL;
+ chunk->v.ioaddr) {
+ iounmap(chunk->v.ioaddr);
+ chunk->v.ioaddr = NULL;
} else {
- if (!ab->qmi.target_mem[i].v.addr)
+ if (!chunk->v.addr)
continue;
dma_free_coherent(ab->dev,
- ab->qmi.target_mem[i].prev_size,
- ab->qmi.target_mem[i].v.addr,
- ab->qmi.target_mem[i].paddr);
- ab->qmi.target_mem[i].v.addr = NULL;
+ chunk->prev_size,
+ chunk->v.addr,
+ chunk->paddr);
+ chunk->v.addr = NULL;
}
+
+ chunk->paddr = 0;
+ chunk->size = 0;
}
}
--
2.25.1
next prev parent reply other threads:[~2026-07-30 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 6:17 [PATCH ath-next 0/3] wifi: ath12k: align QMI memory to 64 KB boundary Baochen Qiang
2026-07-30 6:17 ` [PATCH ath-next 1/3] wifi: ath12k: use per-device max QMI chunk size Baochen Qiang
2026-07-30 6:17 ` Baochen Qiang [this message]
2026-07-30 6:17 ` [PATCH ath-next 3/3] wifi: ath12k: align QMI target memory to 64 KB Baochen Qiang
2026-08-19 7:09 ` [PATCH ath-next 0/3] wifi: ath12k: align QMI memory to 64 KB boundary Rameshkumar Sundaram
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=20260730-ath12k-align-qmi-memory-v1-2-0fef98dda614@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@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