of/device: Update dma_range_map only when dev has valid dma-ranges
The commit e0d07278 ("dma-mapping: introduce DMA range map, supplanting dma_pfn_offset") always update dma_range_map even though it was already set, like in the sunxi_mbus driver. the issue is reported at [1]. This patch avoid this(Updating it only when dev has valid dma-ranges). Meanwhile, dma_range_map contains the devices' dma_ranges information, This patch moves dma_range_map before of_iommu_configure. The iommu driver may need to know the dma_address requirements of its iommu consumer devices. [1] https://lore.kernel.org/linux-arm-kernel/5c7946f3-b56e-da00-a750-be097c7ceb32@arm.com/ CC: Frank Rowand <frowand.list@gmail.com> Fixes: e0d07278 ("dma-mapping: introduce DMA range map, supplanting dma_pfn_offset"), Suggested-by:Robin Murphy <robin.murphy@arm.com> Signed-off-by:
Yong Wu <yong.wu@mediatek.com> Signed-off-by:
Paul Kocialkowski <paul.kocialkowski@bootlin.com> Reviewed-by:
Rob Herring <robh@kernel.org> Reviewed-by:
Robin Murphy <robin.murphy@arm.com> Signed-off-by:
Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20210119105203.15530-1-yong.wu@mediatek.com
parent
30596ae0
Please register or sign in to comment