diff options
| author | John Garry <john.g.garry@oracle.com> | 2026-07-14 08:44:56 +0000 |
|---|---|---|
| committer | Ulf Hansson <ulfh@kernel.org> | 2026-07-16 15:17:03 +0200 |
| commit | 5608386899d9de8030980bce3d05bded28f9bfb8 (patch) | |
| tree | af3f437607288d3671c6e3c293f9f80e540c661f /tools/perf/scripts/python/task-analyzer.py | |
| parent | cf93175e7e9fa811d0e9d1f84cae6b35ba25d818 (diff) | |
mmc: bcm2835: DMA mapping improvements
As pointed out by sashiko bot in [0], recent proposed changes to
dma_max_mapping_size() may affect the driver.
While the issue reported may be a false positive, Robin pointed out some
other DMA-related issues in the driver which are addressed here:
- the DMA max mapping size is irrelevant for the programmed IO mode of
operation
- we should not call dma_max_mapping_size() on the MMC host platform
device, but rather the DMA engine device
In addition, it's better to use the device returned from
dmaengine_get_dma_device() for dma_umap_sg() and dma_unmap_sg(), and not
reference the DMA channel device directly.
[0] https://lore.kernel.org/linux-scsi/d82926fe-4557-401d-ae58-4302fef5657c@oracle.com/#t
Signed-off-by: John Garry <john.g.garry@oracle.com>
Signed-off-by: Ulf Hansson <ulfh@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions
