Re: [PATCH 2/2] of: Restrict DMA configuration

2017-08-25 Thread Christoph Hellwig
On Tue, Aug 15, 2017 at 09:19:50AM -0500, Rob Herring wrote: > > For the immediate issue at hand, I guess the alternative plan of attack > > would be to stick a flag in struct bus_type for the bus drivers > > themselves to opt into generic DMA configuration. That at least keeps > > everything

Re: [PATCH 2/2] of: Restrict DMA configuration

2017-08-15 Thread Rob Herring
On Tue, Aug 15, 2017 at 5:18 AM, Robin Murphy wrote: > On 14/08/17 21:08, Rob Herring wrote: >> +linuxppc-dev >> >> On Fri, Aug 11, 2017 at 11:29 AM, Robin Murphy wrote: >>> Moving DMA configuration to happen later at driver probe time had the >>>

Re: [PATCH 2/2] of: Restrict DMA configuration

2017-08-15 Thread Robin Murphy
On 14/08/17 21:08, Rob Herring wrote: > +linuxppc-dev > > On Fri, Aug 11, 2017 at 11:29 AM, Robin Murphy wrote: >> Moving DMA configuration to happen later at driver probe time had the >> unnoticed side-effect that we now perform DMA configuration for *every* >> device

Re: [PATCH 2/2] of: Restrict DMA configuration

2017-08-14 Thread Rob Herring
+linuxppc-dev On Fri, Aug 11, 2017 at 11:29 AM, Robin Murphy wrote: > Moving DMA configuration to happen later at driver probe time had the > unnoticed side-effect that we now perform DMA configuration for *every* > device represented in DT, rather than only those