From: Baochen Qiang <quic_bqiang@quicinc.com>
To: Johan Hovold <johan@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Stephan Gerhold <stephan.gerhold@linaro.org>,
<ath12k@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath12k: extend dma mask to 36 bits
Date: Mon, 24 Mar 2025 16:29:49 +0800 [thread overview]
Message-ID: <a661f86c-7ecc-46fc-a3af-90ad05a0c603@quicinc.com> (raw)
In-Reply-To: <Z-EV21KDfMHds73Q@hovoldconsulting.com>
On 3/24/2025 4:20 PM, Johan Hovold wrote:
> On Mon, Mar 24, 2025 at 04:05:33PM +0800, Baochen Qiang wrote:
>> On 3/24/2025 3:40 PM, Johan Hovold wrote:
>>> On Mon, Mar 24, 2025 at 11:06:16AM +0800, Baochen Qiang wrote:
>>>> On 3/22/2025 12:23 AM, Johan Hovold wrote:
>>>>> Extend the DMA mask to 36 bits to avoid using bounce buffers on machines
>>>>> without an iommu (under OS control) similar to what was done for ath11k
>>>>> in commit dbd73acb22d8 ("wifi: ath11k: enable 36 bit mask for stream
>>>>> DMA").
>>>>>
>>>>> This specifically avoids using bounce buffers on Qualcomm Snapdragon X
>>>>> Elite machines like the Lenovo ThinkPad T14s when running at EL1.
>
>>>>> Note that the mask could possibly be extended further but unresolved DMA
>>>>> issues with 64 GiB X Elite machines currently prevents that from being
>>>>> tested.
>>>>
>>>> could you help elaborate how it could be extended?
>>>
>>> The mask should reflect the capability of the device. That may be
>>> 64 (or 40) bits, but I've only been able to test using 36 bits.
>>
>> are you talking about QCN9274? As far as I know, WCN7850 does not support 40 bits or more.
>
> Or really all devices handled by ath12k since they at least currently
> use a common mask.
>
> The T14s has a:
>
> 0004:01:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01)
>
> ath12k_pci 0004:01:00.0: Hardware name: wcn7850 hw2.0
> ath12k_pci 0004:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200
>
> Sounds like 36 bits is the correct choice for now then.
yes, let's keep it as 36 for now.
>
> Johan
next prev parent reply other threads:[~2025-03-24 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 16:23 Johan Hovold
2025-03-24 3:06 ` Baochen Qiang
2025-03-24 7:40 ` Johan Hovold
2025-03-24 8:05 ` Baochen Qiang
2025-03-24 8:20 ` Johan Hovold
2025-03-24 8:29 ` Baochen Qiang [this message]
2025-03-24 8:33 ` Baochen Qiang
2025-03-24 9:18 ` Johan Hovold
[not found] ` <b1e44988-a80c-4e60-a093-434e0834aa1a@quicinc.com>
2025-03-26 4:29 ` Vasanthakumar Thiagarajan
2025-03-26 15:11 ` Jeff Johnson
2025-03-26 15:16 ` Johan Hovold
2025-03-26 15:41 ` Jeff Johnson
2025-03-27 22:58 ` Jeff Johnson
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=a661f86c-7ecc-46fc-a3af-90ad05a0c603@quicinc.com \
--to=quic_bqiang@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stephan.gerhold@linaro.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®