dma-buf: add dma_data_direction to unmap dma_buf_op

Some exporters may use DMA map/unmap APIs in dma-buf ops, which require
enum dma_data_direction for both map and unmap operations.

Thus, the unmap dma_buf_op also needs to have enum dma_data_direction as
a parameter.

Reported-by: Tomasz Stanislawski <t.stanislaws@samsung.com>
Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>

1 files changed, 5 insertions, 2 deletions

diff --git a/drivers/base/dma-buf.c b/drivers/base/dma-buf.c
index 8afe2dd1791..c9a945fd1a0 100644
--- a/drivers/base/dma-buf.c
+++ b/drivers/base/dma-buf.c
@@ -271,16 +271,19 @@ EXPORT_SYMBOL_GPL(dma_buf_map_attachment);
  * dma_buf_ops.
  * @attach:     [in]    attachment to unmap buffer from
  * @sg_table:   [in]    scatterlist info of the buffer to unmap
+ * @direction:  [in]    direction of DMA transfer
  *
  */
 void dma_buf_unmap_attachment(struct dma_buf_attachment *attach,
-                                struct sg_table *sg_table)
+                                struct sg_table *sg_table,
+                                enum dma_data_direction direction)
 {
         if (WARN_ON(!attach || !attach->dmabuf || !sg_table))
                 return;
 
         mutex_lock(&attach->dmabuf->lock);
-        attach->dmabuf->ops->unmap_dma_buf(attach, sg_table);
+        attach->dmabuf->ops->unmap_dma_buf(attach, sg_table,
+                                                direction);
         mutex_unlock(&attach->dmabuf->lock);
 
 }