Re: dmaengine for sh7760 (was Re: use the generic dma-noncoherent code for sh V2)

2018-08-20 Thread Arnd Bergmann
On Sun, Aug 19, 2018 at 7:38 AM Rob Landley wrote: > > On 08/17/2018 03:23 PM, Arnd Bergmann wrote: > > On Fri, Aug 17, 2018 at 7:04 PM Rob Landley wrote: > >> On 07/31/2018 07:56 AM, Arnd Bergmann wrote: > >>> On Fri, Jul 27, 2018 at 6:20 PM, Rob Landley wrote: > On 07/24/2018 03:21 PM,

Re: dmaengine for sh7760 (was Re: use the generic dma-noncoherent code for sh V2)

2018-08-18 Thread Rob Landley
On 08/17/2018 03:23 PM, Arnd Bergmann wrote: > On Fri, Aug 17, 2018 at 7:04 PM Rob Landley wrote: >> On 07/31/2018 07:56 AM, Arnd Bergmann wrote: >>> On Fri, Jul 27, 2018 at 6:20 PM, Rob Landley wrote: On 07/24/2018 03:21 PM, Christoph Hellwig wrote: > On Tue, Jul 24, 2018 at 02:01:42PM

Re: dmaengine for sh7760 (was Re: use the generic dma-noncoherent code for sh V2)

2018-08-17 Thread Arnd Bergmann
On Fri, Aug 17, 2018 at 7:04 PM Rob Landley wrote: > On 07/31/2018 07:56 AM, Arnd Bergmann wrote: > > On Fri, Jul 27, 2018 at 6:20 PM, Rob Landley wrote: > >> On 07/24/2018 03:21 PM, Christoph Hellwig wrote: > >>> On Tue, Jul 24, 2018 at 02:01:42PM +0200, Christoph Hellwig wrote: > Hi all,

dmaengine for sh7760 (was Re: use the generic dma-noncoherent code for sh V2)

2018-08-17 Thread Rob Landley
On 07/31/2018 07:56 AM, Arnd Bergmann wrote: > On Fri, Jul 27, 2018 at 6:20 PM, Rob Landley wrote: >> On 07/24/2018 03:21 PM, Christoph Hellwig wrote: >>> On Tue, Jul 24, 2018 at 02:01:42PM +0200, Christoph Hellwig wrote: Hi all, can you review these patches to switch sh to use

Re: use the generic dma-noncoherent code for sh V2

2018-07-31 Thread Arnd Bergmann
On Mon, Jul 30, 2018 at 11:06 AM, Christoph Hellwig wrote: > On Fri, Jul 27, 2018 at 11:20:21AM -0500, Rob Landley wrote: >> Speaking of DMA: > > Which really has nothing to do with the dma mapping code, which > also means I can't help you much unfortunately. > > That being said sh is the last

Re: use the generic dma-noncoherent code for sh V2

2018-07-31 Thread Arnd Bergmann
On Fri, Jul 27, 2018 at 6:20 PM, Rob Landley wrote: > On 07/24/2018 03:21 PM, Christoph Hellwig wrote: >> On Tue, Jul 24, 2018 at 02:01:42PM +0200, Christoph Hellwig wrote: >>> Hi all, >>> >>> can you review these patches to switch sh to use the generic >>> dma-noncoherent code? All the

Re: use the generic dma-noncoherent code for sh V2

2018-07-30 Thread Geert Uytterhoeven
Hi Rob, CC Guennadi On Fri, Jul 27, 2018 at 6:21 PM Rob Landley wrote: > On 07/24/2018 03:21 PM, Christoph Hellwig wrote: > > On Tue, Jul 24, 2018 at 02:01:42PM +0200, Christoph Hellwig wrote: > >> can you review these patches to switch sh to use the generic > >> dma-noncoherent code? All the

Re: use the generic dma-noncoherent code for sh V2

2018-07-30 Thread Christoph Hellwig
On Fri, Jul 27, 2018 at 11:20:21AM -0500, Rob Landley wrote: > Speaking of DMA: Which really has nothing to do with the dma mapping code, which also means I can't help you much unfortunately. That being said sh is the last pending of the initial dma-noncoherent conversion, I'd greatly appreciate

Re: use the generic dma-noncoherent code for sh V2

2018-07-27 Thread Rob Landley
On 07/24/2018 03:21 PM, Christoph Hellwig wrote: > On Tue, Jul 24, 2018 at 02:01:42PM +0200, Christoph Hellwig wrote: >> Hi all, >> >> can you review these patches to switch sh to use the generic >> dma-noncoherent code? All the requirements are in mainline already >> and we've switched various

Re: use the generic dma-noncoherent code for sh V2

2018-07-24 Thread Christoph Hellwig
Ok, there is one more issue with this version. Wait for a new one tomorrow. On Tue, Jul 24, 2018 at 02:01:42PM +0200, Christoph Hellwig wrote: > Hi all, > > can you review these patches to switch sh to use the generic > dma-noncoherent code? All the requirements are in mainline already > and

use the generic dma-noncoherent code for sh V2

2018-07-24 Thread Christoph Hellwig
Hi all, can you review these patches to switch sh to use the generic dma-noncoherent code? All the requirements are in mainline already and we've switched various architectures over to it already. Changes since V1: - fixed two stupid compile errors and verified them using a local cross