Re: [PATCH V10 00/12] IOMMU probe deferral support

2017-04-06 Thread Frank Rowand
On 04/04/17 18:23, Rob Herring wrote: > On Tue, Apr 4, 2017 at 5:18 AM, Sricharan R wrote: >> This series calls the dma ops configuration for the devices >> at a generic place so that it works for all busses. >> The dma_configure_ops for a device is now called during >>

Re: [PATCH V10 00/12] IOMMU probe deferral support

2017-04-05 Thread Lorenzo Pieralisi
On Tue, Apr 04, 2017 at 01:49:29PM +0100, Robin Murphy wrote: > On 04/04/17 11:18, Sricharan R wrote: > > This series calls the dma ops configuration for the devices > > at a generic place so that it works for all busses. > > The dma_configure_ops for a device is now called during > > the

Re: [PATCH V10 00/12] IOMMU probe deferral support

2017-04-04 Thread Rob Herring
On Tue, Apr 4, 2017 at 5:18 AM, Sricharan R wrote: > This series calls the dma ops configuration for the devices > at a generic place so that it works for all busses. > The dma_configure_ops for a device is now called during > the device_attach callback just before the

Re: [PATCH V10 00/12] IOMMU probe deferral support

2017-04-04 Thread Robin Murphy
On 04/04/17 11:18, Sricharan R wrote: > This series calls the dma ops configuration for the devices > at a generic place so that it works for all busses. > The dma_configure_ops for a device is now called during > the device_attach callback just before the probe of the > bus/driver is called.

[PATCH V10 00/12] IOMMU probe deferral support

2017-04-04 Thread Sricharan R
This series calls the dma ops configuration for the devices at a generic place so that it works for all busses. The dma_configure_ops for a device is now called during the device_attach callback just before the probe of the bus/driver is called. Similarly dma_deconfigure is called during