iommu: Disable on !MMU builds
authorArnd Bergmann <arnd@arndb.de>
Wed, 28 Jan 2015 14:45:53 +0000 (15:45 +0100)
committerJoerg Roedel <jroedel@suse.de>
Fri, 30 Jan 2015 12:39:28 +0000 (13:39 +0100)
commite5144c9375851948f50e13db80c3150e3a7521b8
treea756408b0c739fda3a360592e52983d53679f00b
parent860cd64d102d9b6c97830e09c447a9a850ea7641
iommu: Disable on !MMU builds

A lot of the IOMMU support code does not build if the CPU does
not have an MMU itself, and it's not clear if there is any
use case for it, so let's just disable it and wait for anybody
to need it.

This avoids randconfig errors like

../arch/arm/mm/dma-mapping.c: In function '__iommu_alloc_remap':
../arch/arm/mm/dma-mapping.c:1278:34: error: 'VM_ARM_DMA_CONSISTENT' undeclared (first use in this function)
  area = get_vm_area_caller(size, VM_ARM_DMA_CONSISTENT | VM_USERMAP,
                                  ^
../arch/arm/mm/dma-mapping.c:1278:34: note: each undeclared identifier is reported only once for each function it appears in
../arch/arm/mm/dma-mapping.c: In function '__atomic_get_pages':
../arch/arm/mm/dma-mapping.c:1358:27: error: 'atomic_pool' undeclared (first use in this function)
  struct dma_pool *pool = &atomic_pool;

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
drivers/iommu/Kconfig