iommu/omap: Fix map protection value handling
authorLaurent Pinchart <laurent.pinchart@ideasonboard.com>
Fri, 7 Mar 2014 23:44:38 +0000 (00:44 +0100)
committerLaurent Pinchart <laurent.pinchart@ideasonboard.com>
Wed, 16 Apr 2014 14:30:18 +0000 (16:30 +0200)
commit286f600bc890347f7ec7bd50d33210d53a9095a3
treee6af94983a711b69aeb5f5208fc6082d3ab3442d
parent67b779d28d6e8afdd79a70423324273018114cad
iommu/omap: Fix map protection value handling

The prot flags passed to the IOMMU map handler are defined in
include/linux/iommu.h as IOMMU_(READ|WRITE|CACHE|EXEC). However, the
driver expects to receive MMU_RAM_* OMAP-specific flags. This causes
IOMMU flags being interpreted as page sizes, leading to failures.

Hardcode the OMAP mapping parameters to little-endian, 8-bits and
non-mixed page attributes. Furthermore, as the OMAP IOMMU doesn't
support read-only or write-only mappings, ignore the prot value.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Sakari Ailus <sakari.ailus@iki.fi>
Acked-by: Suman Anna <s-anna@ti.com>
drivers/iommu/omap-iommu.c
This page took 0.025514 seconds and 5 git commands to generate.