Re: [PATCH 01/12] i2c: qup: fixed releasing dma without flush operation completion

2018-02-27 Thread Andy Gross
On Sat, Feb 03, 2018 at 01:28:06PM +0530, Abhishek Sahu wrote: > The QUP BSLP BAM generates the following error sometimes if the > current I2C DMA transfer fails and the flush operation has been > scheduled > > “bam-dma-engine 7884000.dma: Cannot free busy channel” > > If any I2C error comes

Re: [PATCH 01/12] i2c: qup: fixed releasing dma without flush operation completion

2018-02-27 Thread Christ, Austin
Tested on Centriq 2400 Reviewed-by: Austin Christ On 2/3/2018 12:58 AM, Abhishek Sahu wrote: The QUP BSLP BAM generates the following error sometimes if the current I2C DMA transfer fails and the flush operation has been scheduled “bam-dma-engine 7884000.dma: Cannot free busy channel” I

Re: [PATCH 01/12] i2c: qup: fixed releasing dma without flush operation completion

2018-02-19 Thread Abhishek Sahu
On 2018-02-08 19:33, Sricharan R wrote: Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: The QUP BSLP BAM generates the following error sometimes if the current I2C DMA transfer fails and the flush operation has been scheduled “bam-dma-engine 7884000.dma: Cannot free busy channel” I

Re: [PATCH 01/12] i2c: qup: fixed releasing dma without flush operation completion

2018-02-08 Thread Sricharan R
Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > The QUP BSLP BAM generates the following error sometimes if the > current I2C DMA transfer fails and the flush operation has been > scheduled > > “bam-dma-engine 7884000.dma: Cannot free busy channel” > > If any I2C error comes during

[PATCH 01/12] i2c: qup: fixed releasing dma without flush operation completion

2018-02-02 Thread Abhishek Sahu
The QUP BSLP BAM generates the following error sometimes if the current I2C DMA transfer fails and the flush operation has been scheduled “bam-dma-engine 7884000.dma: Cannot free busy channel” If any I2C error comes during BAM DMA transfer, then the QUP I2C interrupt will be generated and the