From: <ckim@etri.re.kr>
To: <kernelnewbies@kernelnewbies.org>
Subject: a question about dma_set_mask function
Date: Thu, 22 Jul 2021 16:33:13 +0900 [thread overview]
Message-ID: <00a201d77ecb$d4339490$7c9abdb0$@etri.re.kr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1661 bytes --]
Hello,
I have a question about DNA (I was reading DMA-API-HOWTO.txt
<https://www.kernel.org/doc/Documentation/DMA-API-HOWTO.txt> ).
You know regarding DMA, there is cpu virtual address, cpu physical address
and bus address for the device.
Bus address is converted to cpu physical address using bridge or bus
controller to which the device is attached.
And for platform device, bus address is equal to the cpu physical address.
The DMA-API-HOWTO.txt
<https://www.kernel.org/doc/Documentation/DMA-API-HOWTO.txt> says
> When dma_set_mask() or dma_set_mask_and_coherent() is successful, and
> returns zero, the kernel saves away this mask you have provided. The
> kernel will use this information later when you make DMA mappings.
So I guess when the driver later requests memory for dma using
dma_map_..(ex. dma_map_single, or dma_map_sg) function,
the kernel allocates memory and sets up page table and it sets the bus
address in the ranges supported by the dma_mask.
The virtual address is returned by the function, but where is this 'bus
address' kept? I see a pointer to the struct page in the function argument,
Is it kept in this struct array? Or is the bus address just the physical
address(pfn) in the page table?(I guess so)
And when the device has a separate iommu(like arm64's SMMU), I guess the DMA
virtual address (assigned for dma by the kernel) for the device is first
converted to the bus address by iommu and then the bus address is converted
to physical address by bus bridge. Is my understanding correct?
It's so confusing.. Any explanation or comment will be deeply appreciated.
Thanks!
Chan Kim
[-- Attachment #1.2: Type: text/html, Size: 4891 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2021-07-22 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 7:33 ckim [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-22 8:06 a question about dma_set_mask function ckim
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='00a201d77ecb$d4339490$7c9abdb0$@etri.re.kr' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.