From: Guenter Roeck <linux@roeck-us.net>
To: Thierry Reding <treding@nvidia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpu: host1x: Use direct DMA with IOMMU API usage
Date: Wed, 6 Feb 2019 14:08:33 -0800 [thread overview]
Message-ID: <20190206220833.GA20747@roeck-us.net> (raw)
On Fri, Feb 01, 2019 at 02:28:26PM +0100, Thierry Reding wrote:
> If we use the IOMMU API directly to map buffers into host1x' IOVA space,
> we must make sure that the DMA API doesn't already set up a mapping, or
> else translation will fail.
>
> The direct DMA API allows us to allocate memory that will not be mapped
> through an IOMMU automatically.
>
> Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
arm64:defconfig:
ERROR: "dma_direct_free" [drivers/gpu/host1x/host1x.ko] undefined!
ERROR: "dma_direct_alloc" [drivers/gpu/host1x/host1x.ko] undefined!
Guenter
> ---
> drivers/gpu/host1x/cdma.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/host1x/cdma.c b/drivers/gpu/host1x/cdma.c
> index 64099cc1964b..e22c1133a4c5 100644
> --- a/drivers/gpu/host1x/cdma.c
> +++ b/drivers/gpu/host1x/cdma.c
> @@ -19,6 +19,7 @@
>
> #include <asm/cacheflush.h>
> #include <linux/device.h>
> +#include <linux/dma-direct.h>
> #include <linux/dma-mapping.h>
> #include <linux/host1x.h>
> #include <linux/interrupt.h>
> @@ -70,6 +71,7 @@ static void host1x_pushbuffer_destroy(struct push_buffer *pb)
> */
> static int host1x_pushbuffer_init(struct push_buffer *pb)
> {
> + unsigned long attrs = DMA_ATTR_WRITE_COMBINE;
> struct host1x_cdma *cdma = pb_to_cdma(pb);
> struct host1x *host1x = cdma_to_host1x(cdma);
> struct iova *alloc;
> @@ -91,8 +93,8 @@ static int host1x_pushbuffer_init(struct push_buffer *pb)
>
> size = iova_align(&host1x->iova, size);
>
> - pb->mapped = dma_alloc_wc(host1x->dev, size, &pb->phys,
> - GFP_KERNEL);
> + pb->mapped = dma_direct_alloc(host1x->dev, size, &pb->phys,
> + GFP_KERNEL, attrs);
> if (!pb->mapped)
> return -ENOMEM;
>
> @@ -127,7 +129,10 @@ static int host1x_pushbuffer_init(struct push_buffer *pb)
> iommu_free_iova:
> __free_iova(&host1x->iova, alloc);
> iommu_free_mem:
> - dma_free_wc(host1x->dev, size, pb->mapped, pb->phys);
> + if (host1x->domain)
> + dma_direct_free(host1x->dev, size, pb->mapped, pb->phys, attrs);
> + else
> + dma_free_wc(host1x->dev, size, pb->mapped, pb->phys);
>
> return err;
> }
> --
> 2.7.4
next reply other threads:[~2019-02-06 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 22:08 Guenter Roeck [this message]
2019-02-07 8:51 ` [PATCH] gpu: host1x: Use direct DMA with IOMMU API usage Thierry Reding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190206220833.GA20747@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=treding@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox