Re: [Freedreno] [PATCH v3 2/2] drm/msm/a6xx: Use the DMA API for GMU memory objects

2020-03-02 Thread Ruhl, Michael J
>-Original Message- >From: dri-devel On Behalf Of >Jordan Crouse >Sent: Monday, March 2, 2020 1:24 PM >To: linux-arm-...@vger.kernel.org >Cc: David Airlie ; freedreno@lists.freedesktop.org; >smase...@codeaurora.org; linux-ker...@vger.kernel.org; dri- >de...@lists.freedesktop.org; Douglas A

Re: [Freedreno] [PATCH v3 2/2] drm/msm/a6xx: Use the DMA API for GMU memory objects

2020-03-02 Thread Jordan Crouse
On Mon, Mar 02, 2020 at 06:56:47PM +, Ruhl, Michael J wrote: > >-Original Message- > >From: dri-devel On Behalf Of > >Jordan Crouse > >Sent: Monday, March 2, 2020 1:24 PM > >To: linux-arm-...@vger.kernel.org > >Cc: David Airlie ; freedreno@lists.freedesktop.org; > >smase...@codeaurora.

[Freedreno] [PATCH v3 2/2] drm/msm/a6xx: Use the DMA API for GMU memory objects

2020-03-02 Thread Jordan Crouse
The GMU has very few memory allocations and uses a flat memory space so there is no good reason to go out of our way to bypass the DMA APIs which were basically designed for this exact scenario. v3: Set the dma mask correctly and use dma_addr_t for the iova type v2: Pass force_dma false to of_dma