[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210312163626.GA2655841@infradead.org>
Date: Fri, 12 Mar 2021 16:36:26 +0000
From: Christoph Hellwig <hch@...radead.org>
To: Paul Cercueil <paul@...pouillou.net>
Cc: Christoph Hellwig <hch@...radead.org>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Sam Ravnborg <sam@...nborg.org>, od@...c.me,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
linux-mips@...r.kernel.org
Subject: Re: [PATCH v2 3/5] drm: Add and export function
drm_gem_cma_mmap_noncoherent
On Thu, Mar 11, 2021 at 04:12:55PM +0000, Paul Cercueil wrote:
> ret = dma_mmap_pages(cma_obj->base.dev->dev,
> vma, vma->vm_end - vma->vm_start,
> virt_to_page(cma_obj->vaddr));
>
> It works fine.
>
> I think I can use remap_pfn_range() for now, and switch to your new API once
> it's available in drm-misc-next.
No, drivers must not use dma_to_phys, and they also must not include
dma-direct.h.
Powered by blists - more mailing lists