Re: [PATCH] dmatest: terminate all ongoing transfers before submitting new one

2012-10-16 Thread Andy Shevchenko
On Tue, Oct 16, 2012 at 12:52 PM, Viresh Kumar wrote: >>> Also, the proposed solution might hide some other important errors. We may >>> need >>> to terminate transfers when we found that an error is there in last >>> transfers: >> I think it could be better than first solution, but what do you

Re: [PATCH] dmatest: terminate all ongoing transfers before submitting new one

2012-10-16 Thread Viresh Kumar
Hi Andy, Adding blank lines before and after your replies makes it more readable. On 16 October 2012 15:05, Andy Shevchenko wrote: > On Tue, Oct 16, 2012 at 11:56 AM, viresh kumar > wrote: >> Can you try with a large timeout value for the module. > I tried and the failures were gone. Ok. So t

Re: [PATCH] dmatest: terminate all ongoing transfers before submitting new one

2012-10-16 Thread Andy Shevchenko
On Tue, Oct 16, 2012 at 11:56 AM, viresh kumar wrote: > On Tue, Oct 16, 2012 at 2:15 PM, Andy Shevchenko > wrote: >> The following error messages come if we have software LLP emulation enabled >> and >> enough threads running. >> >> modprobe dmatest iterations=40 >> [ 168.048601] dmatest: Start

Re: [PATCH] dmatest: terminate all ongoing transfers before submitting new one

2012-10-16 Thread viresh kumar
On Tue, Oct 16, 2012 at 2:15 PM, Andy Shevchenko wrote: > The following error messages come if we have software LLP emulation enabled > and > enough threads running. > > modprobe dmatest iterations=40 > [ 168.048601] dmatest: Started 1 threads using dma0chan0 > [ 168.054546] dmatest: Started 1

[PATCH] dmatest: terminate all ongoing transfers before submitting new one

2012-10-16 Thread Andy Shevchenko
The following error messages come if we have software LLP emulation enabled and enough threads running. modprobe dmatest iterations=40 [ 168.048601] dmatest: Started 1 threads using dma0chan0 [ 168.054546] dmatest: Started 1 threads using dma0chan1 [ 168.060441] dmatest: Started 1 threads using