summaryrefslogtreecommitdiff
path: root/Documentation/core-api
diff options
context:
space:
mode:
authorJohn Garry <john.garry@linux.dev>2026-08-31 09:36:20 +0000
committerMarek Szyprowski <m.szyprowski@samsung.com>2026-09-07 18:55:12 +0200
commit95d2fec40c483d8a63e5ffa0fa88faeb2e0ed462 (patch)
tree8ea38cbf8f312c7a003e08dd88c304574fd9577f /Documentation/core-api
parentcee9395acd8043be0644b25c34bfa86623f2b935 (diff)
downloadlinux-next-95d2fec40c483d8a63e5ffa0fa88faeb2e0ed462.tar.gz
linux-next-95d2fec40c483d8a63e5ffa0fa88faeb2e0ed462.zip
dma-mapping: rename dma_opt_mapping_size()
Function dma_opt_mapping_size() implies from its name that it returns a target or sweet spot DMA mapping size. However, it is just an upper limit optimal DMA mapping size. Above this size, DMA mapping performance may significantly degrade. Rename to dma_max_opt_mapping_size() to reflect the real behaviour. Also rename the internal DMA mapping symbols to align with this. The DMA API documentation already described this behaviour properly (so there is nothing to update). Signed-off-by: John Garry <john.garry@linux.dev> Link: https://lore.kernel.org/r/20260831093620.3481337-1-john.g.garry@oracle.com Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Diffstat (limited to 'Documentation/core-api')
-rw-r--r--Documentation/core-api/dma-api.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/core-api/dma-api.rst b/Documentation/core-api/dma-api.rst
index ba23a472f794..69d4ebe4f96d 100644
--- a/Documentation/core-api/dma-api.rst
+++ b/Documentation/core-api/dma-api.rst
@@ -154,7 +154,7 @@ others should not be larger than the returned value.
::
size_t
- dma_opt_mapping_size(struct device *dev);
+ dma_max_opt_mapping_size(struct device *dev);
Returns the maximum optimal size of a mapping for the device.