Re: [PATCH 5/5] iommu/omap: Fix map protection value handling

2014-03-14 Thread Laurent Pinchart
Hi Suman, Thank you for the review. On Thursday 13 March 2014 19:07:33 Suman Anna wrote: On 03/07/2014 06:46 PM, Laurent Pinchart wrote: 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

Re: [PATCH 5/5] iommu/omap: Fix map protection value handling

2014-03-14 Thread Suman Anna
Hi Laurent, On 03/14/2014 04:46 AM, Laurent Pinchart wrote: Hi Suman, Thank you for the review. On Thursday 13 March 2014 19:07:33 Suman Anna wrote: On 03/07/2014 06:46 PM, Laurent Pinchart wrote: The prot flags passed to the IOMMU map handler are defined in include/linux/iommu.h as

Re: [PATCH 5/5] iommu/omap: Fix map protection value handling

2014-03-13 Thread Suman Anna
Hi Laurent, On 03/07/2014 06:46 PM, Laurent Pinchart wrote: 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

[PATCH 5/5] iommu/omap: Fix map protection value handling

2014-03-07 Thread Laurent Pinchart
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