[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <014526bf-e3e9-bd94-a239-0ec1e7feaf72@nxp.com>
Date: Tue, 4 Jun 2019 14:16:11 +0000
From: Laurentiu Tudor <laurentiu.tudor@....com>
To: Christoph Hellwig <hch@....de>
CC: Greg KH <gregkh@...uxfoundation.org>,
"stern@...land.harvard.edu" <stern@...land.harvard.edu>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"marex@...x.de" <marex@...x.de>, Leo Li <leoyang.li@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"robin.murphy@....com" <robin.murphy@....com>,
"noring@...rew.org" <noring@...rew.org>,
"JuergenUrban@....de" <JuergenUrban@....de>
Subject: Re: [PATCH v7 0/5] prerequisites for device reserved local mem rework
On 31.05.2019 19:43, Christoph Hellwig wrote:
> On Wed, May 29, 2019 at 02:06:12PM +0000, Laurentiu Tudor wrote:
>> Thanks, hope this time everything is fine.
>
> I've applied it to the dma-mapping tree now.
>
>> When you get the time, please let me know your ideas on the next steps.
>
> I think the next step is to move the call to
> dma_alloc_from_dev_coherent from dma_alloc_attrs into the ->alloc
> instances. The only onces that really need it for now are the
> generic and legacy arm dma-direct code, and drivers/iommu/dma-iommu.c
> as well as the ARM DMA API code, as those are the ones use for
> architectures that declare coherent regions. The other iommus are
> not used on OF platforms (at least that's what my analysis said a while
> ago, feel free to double check it)
Thanks for the details. I'll be OOO next week so probably I'll start
looking into it next next week.
---
Best Regards, Laurentiu
Powered by blists - more mailing lists