[RFC 0/5] ARM: dma-mapping: New dma_map_ops to control IOVA more precisely

Krishna Reddy vdumpa at nvidia.com
Fri Sep 21 14:16:00 EDT 2012

> > The device(H/W controller) need to access few special memory
> > blocks(IOVA==PA) and DRAM as well.
> OK, so only /some/ of the VA space is VA==PA, and some is remapped; that's a
> little different that what you originally implied above.
> BTW, which HW module is this; AVP/COP or something else. This sounds like an
> odd requirement.

This is not specific to ARM7. There are protected memory regions on Tegra that
can be accessed by some controllers like display, 2D, 3D, VDE, HDA. These are
DRAM regions configured as protected by BootRom. These memory regions
are not exposed to and not managed by OS page allocator. The H/W controller
 accesses to these regions still to go through IOMMU.
The IOMMU view for all the H/W controllers is not uniform on Tegra.
Some Controllers see entire 4GB IOVA space. i.e all accesses go though IOMMU.
Some controllers see the IOVA Space that don't overlap with MMIO space.  i.e
The MMIO address access bypass IOMMU and directly go to MMIO space.
Tegra IOMMU can support multiple address spaces as well. To hide controller
Specific behavior, the drivers should take care of one to one mapping and
remove inaccessible iova spaces in their address space's based platform device info.

In my initial mail, I referred protected memory regions as MMIO blocks, which
is incorrect.


More information about the linux-arm-kernel mailing list