diff options
| author | Alexandre Courbot <acourbot@nvidia.com> | 2026-08-05 14:01:46 +0900 |
|---|---|---|
| committer | Danilo Krummrich <dakr@kernel.org> | 2026-08-06 22:54:39 +0200 |
| commit | 91645a52ebf2e22f0bd37c142b79238617d38758 (patch) | |
| tree | 5a6d5d3eb35c88bb7731705dccb8ba574c314c63 /scripts | |
| parent | d1dc8faf1152e39070250df714b2d544c8ae32bb (diff) | |
| download | linux-stable-91645a52ebf2e22f0bd37c142b79238617d38758.tar.gz linux-stable-91645a52ebf2e22f0bd37c142b79238617d38758.zip | |
rust: dma: rename dma_handle to dma_address
The `dma_handle` naming is inherited from the C API, but what this
really describes is the device DMA address; everything named
`dma_handle` is actually a `dma_addr_t`.
This naming introduces some confusion on the Rust API side, as handles
are supposed to be opaque tokens, yet we were doing address computation
on values returned by `dma_handle`.
Rename `dma_handle` to `dma_address` while nova-core is still its only
user.
Suggested-by: John Hubbard <jhubbard@nvidia.com>
Suggested-by: Danilo Krummrich <dakr@kernel.org>
Link: https://lore.kernel.org/all/DK75LUA4NLGI.3P29AIZQE20V2@kernel.org/
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
Link: https://patch.msgid.link/20260805-falcon-dma-projections-v2-2-4cc9f3f13ee9@nvidia.com
[ Rebase and fix up build failures due to newly introduced dma_handle()
calls. - Danilo ]
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions