aboutsummaryrefslogtreecommitdiff
path: root/lib/crypto/mpi/mpi-sub-ui.c
diff options
context:
space:
mode:
authorBaruch Siach <[email protected]>2024-09-01 09:12:34 +0300
committerChristoph Hellwig <[email protected]>2024-09-03 10:25:36 +0300
commit122c234ef4e182440f8a60490e9344bfc4e2b5e9 (patch)
tree7fd4f014c919827764234b74b9dfc742fb08af44 /lib/crypto/mpi/mpi-sub-ui.c
parent334304ac2baca7f3e821c47cf5129d90e7a6b1e6 (diff)
arm64: mm: keep low RAM dma zone
Commit ba0fb44aed47 ("dma-mapping: replace zone_dma_bits by zone_dma_limit") optimistically assumed that device-tree dma-ranges property describes the system DMA limits. That assumption ignores DMA limits of individual devices that are not encoded in device tree. Commit 833bd284a45 ("arm64: mm: fix DMA zone when dma-ranges is missing") fixed part of the problem for platforms that do not provide dma-ranges at all. However platforms like SM8550-HDK provide DMA bus limit, but have devices with stronger DMA limits. of_dma_get_max_cpu_address() does not take device limitations into account. These platforms implicitly rely on DMA zone in low 32-bit RAM area. Until we find a better way to figure out the optimal DMA zone range, restore the low RAM DMA zone we had before commit ba0fb44aed47. Fixes: ba0fb44aed47 ("dma-mapping: replace zone_dma_bits by zone_dma_limit") Closes: https://lore.kernel.org/r/[email protected] Reported-by: Neil Armstrong <[email protected]> Reviewed-by: Catalin Marinas <[email protected]> Suggested-by: Robin Murphy <[email protected]> Signed-off-by: Baruch Siach <[email protected]> Tested-by: Neil Armstrong <[email protected]> # on SM8550-HDK Tested-by: Marek Szyprowski <[email protected]> Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'lib/crypto/mpi/mpi-sub-ui.c')
0 files changed, 0 insertions, 0 deletions