From: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
To: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: [PATCH ath-next] wifi: ath12k: fix truncated TX buffer DMA address in MSDU ext descriptor
Date: Wed, 19 Aug 2026 12:43:49 +0530 [thread overview]
Message-ID: <40159684-8324-4c7a-8289-d7a8a17870d2@oss.qualcomm.com> (raw)
In-Reply-To: <20260818-ath12k-truncated-tx-dma-addr-v1-1-ead978969371@oss.qualcomm.com>
On 8/18/2026 7:33 AM, Baochen Qiang wrote:
> ath12k_wifi7_hal_tx_cmd_ext_desc_setup() programs the low 32 bits of the
> TX buffer physical address into HAL_TX_MSDU_EXT_INFO0_BUF_PTR_LO but
> hardcodes the high bits field HAL_TX_MSDU_EXT_INFO1_BUF_PTR_HI to 0x0.
>
> dma_addr_t is 64-bit on platforms with CONFIG_ARCH_DMA_ADDR_T_64BIT, so
> whenever a TX buffer is mapped above the 4 GB boundary the upper bits of
> paddr are dropped and the firmware is handed a truncated address,
> leading to potential TX failures.
>
> Write the upper bits of paddr into BUF_PTR_HI to fix this issue.
>
> Issue found during code review, compile tested only.
>
> Fixes: d889913205cf ("wifi: ath12k: driver for Qualcomm Wi-Fi 7 devices")
> Signed-off-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
Reviewed-by: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
prev parent reply other threads:[~2026-08-19 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 2:03 [PATCH ath-next] wifi: ath12k: fix truncated TX buffer DMA address in MSDU ext descriptor Baochen Qiang
2026-08-19 7:13 ` Rameshkumar Sundaram [this message]
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=40159684-8324-4c7a-8289-d7a8a17870d2@oss.qualcomm.com \
--to=rameshkumar.sundaram@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--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