From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Chan Kim" <ckim@etri.re.kr>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: returned dma address value of dma_alloc_coherent, is it always in the lower 4GB range?
Date: Tue, 14 Mar 2023 01:14:50 -0400 [thread overview]
Message-ID: <687742.1678770890@turing-police> (raw)
In-Reply-To: <034901d955a7$50a377d0$f1ea6770$@etri.re.kr>
[-- Attachment #1.1: Type: text/plain, Size: 781 bytes --]
On Mon, 13 Mar 2023 21:28:28 +0900, "Chan Kim" said:
> which is 32-bit addressable. Even if the device indicates (via the DMA
> mask)
> that it may address the upper 32-bits, consistent allocation will only
> return > 32-bit addresses for DMA if the consistent DMA mask has been
> explicitly changed via dma_set_coherent_mask(). This is true of the
> dma_pool interface as well.
> ------------------------------
> By context I guess it returns the address in lower 32bit address range even
> it the coherent_dma_mask is set to some bigger value.
No, you have that backwards. It's not "even if". It wil give you a 32-bit
address *UNLESS* the driver has called dma_set_coherent_mask() to set a wider
mask *and* the device indicates it supports more than 32 bit addresses...
[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2023-03-14 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 12:28 returned dma address value of dma_alloc_coherent, is it always in the lower 4GB range? Chan Kim
2023-03-14 5:14 ` Valdis Klētnieks [this message]
2023-03-14 8:03 ` Chan Kim
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=687742.1678770890@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=ckim@etri.re.kr \
--cc=kernelnewbies@kernelnewbies.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