From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org, tomi.valkeinen@ti.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] dma-mapping: remove dma_{alloc,free,mmap}_writecombine
Date: Tue, 30 Jul 2019 16:50:45 +0300 [thread overview]
Message-ID: <20190730135045.GA4806@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20190730061849.29686-1-hch@lst.de>
Hi Christoph,
Thank you for the patch.
On Tue, Jul 30, 2019 at 09:18:49AM +0300, Christoph Hellwig wrote:
> We can already use DMA_ATTR_WRITE_COMBINE or the _wc prefixed version,
> so remove the third way of doing things.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/gpu/drm/omapdrm/dss/dispc.c | 11 +++++------
> include/linux/dma-mapping.h | 9 ---------
> 2 files changed, 5 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.c b/drivers/gpu/drm/omapdrm/dss/dispc.c
> index 785c5546067a..c70f3246a552 100644
> --- a/drivers/gpu/drm/omapdrm/dss/dispc.c
> +++ b/drivers/gpu/drm/omapdrm/dss/dispc.c
> @@ -4609,11 +4609,10 @@ static int dispc_errata_i734_wa_init(struct dispc_device *dispc)
> i734_buf.size = i734.ovli.width * i734.ovli.height *
> color_mode_to_bpp(i734.ovli.fourcc) / 8;
>
> - i734_buf.vaddr = dma_alloc_writecombine(&dispc->pdev->dev,
> - i734_buf.size, &i734_buf.paddr,
> - GFP_KERNEL);
> + i734_buf.vaddr = dma_alloc_wc(&dispc->pdev->dev, i734_buf.size,
> + &i734_buf.paddr, GFP_KERNEL);
I would have indented this line to match the rest. Apart from that,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> if (!i734_buf.vaddr) {
> - dev_err(&dispc->pdev->dev, "%s: dma_alloc_writecombine failed\n",
> + dev_err(&dispc->pdev->dev, "%s: dma_alloc_wc failed\n",
> __func__);
> return -ENOMEM;
> }
> @@ -4626,8 +4625,8 @@ static void dispc_errata_i734_wa_fini(struct dispc_device *dispc)
> if (!dispc->feat->has_gamma_i734_bug)
> return;
>
> - dma_free_writecombine(&dispc->pdev->dev, i734_buf.size, i734_buf.vaddr,
> - i734_buf.paddr);
> + dma_free_wc(&dispc->pdev->dev, i734_buf.size, i734_buf.vaddr,
> + i734_buf.paddr);
> }
>
> static void dispc_errata_i734_wa(struct dispc_device *dispc)
> diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h
> index f7d1eea32c78..633dae466097 100644
> --- a/include/linux/dma-mapping.h
> +++ b/include/linux/dma-mapping.h
> @@ -786,9 +786,6 @@ static inline void *dma_alloc_wc(struct device *dev, size_t size,
>
> return dma_alloc_attrs(dev, size, dma_addr, gfp, attrs);
> }
> -#ifndef dma_alloc_writecombine
> -#define dma_alloc_writecombine dma_alloc_wc
> -#endif
>
> static inline void dma_free_wc(struct device *dev, size_t size,
> void *cpu_addr, dma_addr_t dma_addr)
> @@ -796,9 +793,6 @@ static inline void dma_free_wc(struct device *dev, size_t size,
> return dma_free_attrs(dev, size, cpu_addr, dma_addr,
> DMA_ATTR_WRITE_COMBINE);
> }
> -#ifndef dma_free_writecombine
> -#define dma_free_writecombine dma_free_wc
> -#endif
>
> static inline int dma_mmap_wc(struct device *dev,
> struct vm_area_struct *vma,
> @@ -808,9 +802,6 @@ static inline int dma_mmap_wc(struct device *dev,
> return dma_mmap_attrs(dev, vma, cpu_addr, dma_addr, size,
> DMA_ATTR_WRITE_COMBINE);
> }
> -#ifndef dma_mmap_writecombine
> -#define dma_mmap_writecombine dma_mmap_wc
> -#endif
>
> #ifdef CONFIG_NEED_DMA_MAP_STATE
> #define DEFINE_DMA_UNMAP_ADDR(ADDR_NAME) dma_addr_t ADDR_NAME
--
Regards,
Laurent Pinchart
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Christoph Hellwig <hch@lst.de>
Cc: tomi.valkeinen@ti.com, dri-devel@lists.freedesktop.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-mapping: remove dma_{alloc,free,mmap}_writecombine
Date: Tue, 30 Jul 2019 16:50:45 +0300 [thread overview]
Message-ID: <20190730135045.GA4806@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20190730061849.29686-1-hch@lst.de>
Hi Christoph,
Thank you for the patch.
On Tue, Jul 30, 2019 at 09:18:49AM +0300, Christoph Hellwig wrote:
> We can already use DMA_ATTR_WRITE_COMBINE or the _wc prefixed version,
> so remove the third way of doing things.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/gpu/drm/omapdrm/dss/dispc.c | 11 +++++------
> include/linux/dma-mapping.h | 9 ---------
> 2 files changed, 5 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.c b/drivers/gpu/drm/omapdrm/dss/dispc.c
> index 785c5546067a..c70f3246a552 100644
> --- a/drivers/gpu/drm/omapdrm/dss/dispc.c
> +++ b/drivers/gpu/drm/omapdrm/dss/dispc.c
> @@ -4609,11 +4609,10 @@ static int dispc_errata_i734_wa_init(struct dispc_device *dispc)
> i734_buf.size = i734.ovli.width * i734.ovli.height *
> color_mode_to_bpp(i734.ovli.fourcc) / 8;
>
> - i734_buf.vaddr = dma_alloc_writecombine(&dispc->pdev->dev,
> - i734_buf.size, &i734_buf.paddr,
> - GFP_KERNEL);
> + i734_buf.vaddr = dma_alloc_wc(&dispc->pdev->dev, i734_buf.size,
> + &i734_buf.paddr, GFP_KERNEL);
I would have indented this line to match the rest. Apart from that,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> if (!i734_buf.vaddr) {
> - dev_err(&dispc->pdev->dev, "%s: dma_alloc_writecombine failed\n",
> + dev_err(&dispc->pdev->dev, "%s: dma_alloc_wc failed\n",
> __func__);
> return -ENOMEM;
> }
> @@ -4626,8 +4625,8 @@ static void dispc_errata_i734_wa_fini(struct dispc_device *dispc)
> if (!dispc->feat->has_gamma_i734_bug)
> return;
>
> - dma_free_writecombine(&dispc->pdev->dev, i734_buf.size, i734_buf.vaddr,
> - i734_buf.paddr);
> + dma_free_wc(&dispc->pdev->dev, i734_buf.size, i734_buf.vaddr,
> + i734_buf.paddr);
> }
>
> static void dispc_errata_i734_wa(struct dispc_device *dispc)
> diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h
> index f7d1eea32c78..633dae466097 100644
> --- a/include/linux/dma-mapping.h
> +++ b/include/linux/dma-mapping.h
> @@ -786,9 +786,6 @@ static inline void *dma_alloc_wc(struct device *dev, size_t size,
>
> return dma_alloc_attrs(dev, size, dma_addr, gfp, attrs);
> }
> -#ifndef dma_alloc_writecombine
> -#define dma_alloc_writecombine dma_alloc_wc
> -#endif
>
> static inline void dma_free_wc(struct device *dev, size_t size,
> void *cpu_addr, dma_addr_t dma_addr)
> @@ -796,9 +793,6 @@ static inline void dma_free_wc(struct device *dev, size_t size,
> return dma_free_attrs(dev, size, cpu_addr, dma_addr,
> DMA_ATTR_WRITE_COMBINE);
> }
> -#ifndef dma_free_writecombine
> -#define dma_free_writecombine dma_free_wc
> -#endif
>
> static inline int dma_mmap_wc(struct device *dev,
> struct vm_area_struct *vma,
> @@ -808,9 +802,6 @@ static inline int dma_mmap_wc(struct device *dev,
> return dma_mmap_attrs(dev, vma, cpu_addr, dma_addr, size,
> DMA_ATTR_WRITE_COMBINE);
> }
> -#ifndef dma_mmap_writecombine
> -#define dma_mmap_writecombine dma_mmap_wc
> -#endif
>
> #ifdef CONFIG_NEED_DMA_MAP_STATE
> #define DEFINE_DMA_UNMAP_ADDR(ADDR_NAME) dma_addr_t ADDR_NAME
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2019-07-30 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 6:18 [PATCH] dma-mapping: remove dma_{alloc,free,mmap}_writecombine Christoph Hellwig
2019-07-30 6:18 ` Christoph Hellwig
2019-07-30 6:18 ` Christoph Hellwig
2019-07-30 7:50 ` Tomi Valkeinen via iommu
2019-07-30 7:50 ` Tomi Valkeinen
2019-07-30 7:50 ` Tomi Valkeinen
2019-07-30 10:20 ` Christoph Hellwig
2019-07-30 10:20 ` Christoph Hellwig
2019-07-30 11:23 ` Tomi Valkeinen via iommu
2019-07-30 11:23 ` Tomi Valkeinen
2019-07-30 11:23 ` Tomi Valkeinen
2019-07-30 13:50 ` Laurent Pinchart [this message]
2019-07-30 13:50 ` Laurent Pinchart
2019-08-29 14:54 ` Christoph Hellwig
2019-08-29 14:54 ` Christoph Hellwig
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=20190730135045.GA4806@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.